Could you please provide us with the error message you are getting for further debugging.

Also please go through the doc 
https://support.google.com/chrome/answer/111996?hl=en for any help regarding update problems.

@ronefrati : Could you please update on comment #1

Thank you!

When the next beta of 56 I will be able to provide the error message 
meanwhile attached are flags I'm using. Try to rep using this flags.

Deleted: chrome___flags.pdf 303 KB

chrome___flags.pdf 303 KB Download

Google Inc.
‏Copyright 2017 Google Inc.‎. כל הזכויות שמורות.
Google Chrome	56.0.2924.28 (גירסה רשמית) beta (64 סיביות)
גרסה קודמת	5079bb60c246eb7de76df56f3335ef542f87c4c3-refs/branch-heads/2924@{#481}
מערכת הפעלה	Windows 
JavaScript	V8 5.6.326.25
Flash	24.0.0.194
User agent	Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.28 Safari/537.36
שורת פקודה 	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disk-cache-dir="k:\cache" --process-per-site --flag-switches-begin --enable-browser-task-scheduler --enable-device-discovery-notifications --no-pings --disable-javascript-harmony-shipping --enable-new-bookmark-apps --enable-account-consistency --enable-apps-show-on-first-paint --enable-offer-upload-credit-cards --enable-clear-browsing-data-counters --enable-cloud-print-xps --enable-embedded-extension-options --enable-experimental-canvas-features --enable-extension-action-redesign --enable-fast-unload --enable-google-branded-context-menu --google-profile-info --enable-gpu-rasterization --enable-icon-ntp --enable-md-policy-page --enable-message-center-always-scroll-up-upon-notification-removal --new-profile-management --enable-offline-auto-reload --enable-password-generation --enable-permissions-blacklist --enable-print-preview-register-promos --enable-scroll-prediction --enable-single-click-autofill --enable-suggestions-with-substring-match --enable-tab-audio-muting --enable-use-zoom-for-dsf=true --enable-zero-copy --ignore-gpu-blacklist --enable-lcd-text --mhtml-generator-option=skip-nostore-all --nacl-debug-mask=*://*/*debug.nmf --save-page-as-mhtml --secondary-ui-md --show-autofill-type-predictions --enable-smooth-scrolling --top-chrome-md=material-hybrid --try-supported-channel-layouts --enable-features=AutomaticTabDiscarding,FramebustingNeedsSameOriginOrUserGesture,MaterialDesignHistory,MaterialDesignUserMenu,NewAudioRenderingMixingStrategy,OptimizeLoadingIPCForSmallResources,StaleWhileRevalidate2,TranslateLanguageByULP,TranslateUI2016Q2,WebAssembly,WebRTC-H264WithOpenH264FFmpeg,WebUSB,affiliation-based-matching,enable-automatic-password-saving,enable-manual-password-generation,enable-password-force-saving,password-import-export,protect-sync-credential-on-reauth --disable-features=drop-sync-credential --flag-switches-end
נתיב להפעלה	C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
נתיב פרופיל	C:\Users\ronef\AppData\Local\Google\Chrome\User Data\Default
וריאציות	6a89113b-a7aa8ed
d0bd833b-85fb2903
68ebfce2-34df6b5c
90757ebb-f23d1dea
1e528f0f-15305a2
38eb801c-3f4a17df
8364a5c2-7330e714
7c1bc906-f55a7974
2a33b90e-eb524a27
ba3f87da-f23d1dea
a5cb8590-f23d1dea
58aac55e-3f4a17df
f15c1c09-ca7d8d80
9e201a2b-3f4a17df
9d315c2-9597b6c7
5274eb09-3f4a17df
684d1cdf-f23d1dea
8ca44045-f23d1dea
93731dca-3f4a17df
9e5c75f1-5e8029e2
6b121ae7-ca7d8d80
f79cb77b-1963db0f
b7786474-d93a0620
23a898eb-e0e2610f
74df3f1-3f4a17df
4ea303a6-fbb1dc75
7aa46da5-669a04e0
9736de91-3f4a17df
64005e71-fb487281
3326cd71-3f4a17df
ca314179-ea08a3f2
69bf80fa-f23d1dea
b2f0086-93053e47
99c41f12-3f4a17df
7fc902e8-f23d1dea
adda5502-f23d1dea
6844d8aa-669a04e0
3ac60855-486e2a9c
f296190c-cd4ab62e
4442aae2-6e3b1976
ed1d377-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-5c63917a
e7e71889-e1cc0f14
828a5926-8f2c913
Compiler	MSVC 2015 (PGO)

Hi. Could you send the exact error message you see in chrome://help? Thanks.

Why you have not read my previous message :
"When the next beta of 56 I will be able to provide the error message 
meanwhile attached are flags I'm using. Try to rep using this flags."

Yes, thanks, I saw that. We'll wait to hear back from you.

 The installer failed to uncompress archive. Please download Google Chrome again. (קוד שגיאה 7: 0x80040902: 42 -- system level).
Google Chrome

Deleted: Capture.JPG 54.9 KB

	Capture.JPG 54.9 KB View Download

Know after "Reload" it works

Deleted: Capture2.JPG 30.3 KB

	Capture2.JPG 30.3 KB View Download

Could you please do the following and update the thread.

1.Reboot the computer and update chrome again.

2.Also Some antivirus software can prevent Google Chrome from installing on the computer. To check if your antivirus software is the problem, turn it off. Then download Chrome again.

Interesting. Application of the diff patch is failing. The second attempt succeeds because the full installer is used (this is a good thing). I could use some more info to see what might be going on. Would you send me the output of these two commands:

> reg query HKLM\Software\Google\Update /reg:32 /s
> dir "C:\Program Files (x86)\Google\Chrome\Application"

as well as the contents of C:\Windows\Temp\chrome_installer.log and %TEMP%\chrome_installer.log? If you don't want to attach them to the bug, you may send them directly to grt at chromium dot org. Thanks for your help in diagnosing this.

This is the error ( attached )
then Cntrl->F5 resolve the problem

Deleted: Capture.JPG 66.6 KB

	Capture.JPG 66.6 KB View Download

The files U requested

I used my k:\temp for both user and system %TEMP%

Deleted: reg.txt 11.9 KB

reg.txt 11.9 KB View Download

Deleted: dir.txt 614 bytes

dir.txt 614 bytes View Download

Deleted: chrome_installer.log 17.3 KB

chrome_installer.log 17.3 KB View Download

Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for the tidbit about using a different volume for your temp dir. That could be related. How do you pull this off (e.g., by setting the TEMP environment variable, using a junction point, etc)?

TEMP environment

Thanks for the logs. I see that the delta from .51 to .59 failed and that the full updater for .59 succeeded.

+huangs: This looks like C_DISASSEMBLY_FAILED:

[0112/041548.624:ERROR:archive_patch_helper.cc(76)] Failed to apply patch C:\Program Files (x86)\Google\Chrome\Temp\source12452_20256\chrome_patch.diff to file C:\Program Files (x86)\Google\Chrome\Application\56.0.2924.51\Installer\chrome.7z and generating file C:\Program Files (x86)\Google\Chrome\Temp\source12452_20256\chrome.7z using courgette. err=25

Do you know what would cause that?

OP: Do you use any "computer cleaner" programs that might be fiddling with C:\Program Files (x86)\Google\Chrome\Application\56.0.2924.51\Installer\chrome.7z? This is the uncompressed archive against which the updater applies a patch to generate the new archive. Tampering with the original file would make the update fail. It's interesting that patching setup.exe is succeeding. I think %TMP% is a red herring. I don't see that error 42 (APPLY_DIFF_PATCH_FAILED) is spiking in any new way at the moment, so I don't believe we have a new bug in the code that has crept in. Rather, I think you happen to be in the population of users that gets this error for reasons we don't understand. I hope we can get to the bottom of it, as it will be very educational for us.

Hang tight for some more updates and possibly requests for additional info. Thanks for your help.

1. I do not use any "computer cleaner" programs
2. You should check the validity of the chrome.7z before you try incremental update.
3/ You should go to full file download silently to the user without error message to the user.   

Would you use FCIV (https://www.microsoft.com/en-us/download/details.aspx?id=11533) or a similar tool to generate a hash of chrome.7z? Something like this should suffice:

fciv.exe -sha1 "C:\Program Files (x86)\Google\Chrome\Application\56.0.2924.59\Installer\chrome.7z"

I'm curious to see if yours has been modified. If you're able to, please do this before this week's beta refresh.

Automating the retry is a fine idea.

Obviously the  56.0.2924.59 does not exists since I already upgrade 
to 56.0.2924.67
The checksum of 67 is cf0a7ccab7632d4714c70e1297eefa1d6545256f

That's the correct digest, so for the moment let's assume that the input isn't tampered with (I hope it isn't magically modified between now and the next update).

huangs: Any thoughts on how to get actionable info on this failure? I see that courgette:Disassembler has an internal failure reason. Can we surface that in the installer logs? Is there anything else we can do? Would it help to use DumpWithoutCrashing to sample a few of these (I say that without remembering whether or not DWC is wired up in setup.exe :-) ).

// File Checksum Integrity Verifier version 2.05.
//
cf0a7ccab7632d4714c70e1297eefa1d6545256f c:\program files (x86)\google\chrome\application\56.0.2924.67\installer\chrome.7z

 Issue 685574  has been merged into this issue.

Thanks for verifying that the problem is not that the original file has been modified. Are you familiar with Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx)? If you are able to, it would be extremely helpful if you could capture a procmon trace of the next update. Perhaps it would have enough info for me to see what is happening. Capturing a trace is fairly simple:

- Download and install ProcMon
- Launch it. It should automatically start recording.
- Visit chrome://help to trigger an on-demand update check
- Wait for the error message
- Switch back to ProcMon and save the trace.

Once you've done that, please share it with me (grt at chromium dot org) via whatever means you like. Thanks for your help.

Closing due to lack of feedback.