[SOLVED] 2019-12 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4530684) - Install error - 0x800706be

gpatel522 · Dec 14, 2019

Hi,

I've been getting this update error for a while. Also my start menu search and Cortana has stopped working. not sure if these two are related. Can anyone help?

Machine: Windows 10 x64

gpatel522 · Dec 14, 2019

Link to my PML file from ProcMon after the error happens.

Logfile.zip

Sysnative Windows Update · Dec 14, 2019

Hello and welcome!

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

Download the portable version of GSmartControl and save it on your Desktop;
Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
Please note: If the SMART Status reads: Unsupported, stop and let me know.

gpatel522 · Dec 14, 2019

On my main drive (C:):

Complete error log:

SMART Extended Comprehensive Error Log Version: 18 (77 sectors)
No Errors Logged

On a secondary drive (E:)

Complete error log:

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

On a secondary drive (D:)

Complete error log:

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 14628 (device log contains only the most recent 4 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 14628 [3] occurred at disk power-on lifetime: 14302 hours (595 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 06 00 00 00 03 39 2a e0 00 Error: UNC 6 sectors at LBA = 0x0003392a = 211242

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 00 00 03 39 28 e0 00 01:32:24.300 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 20 e0 00 01:32:19.600 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 18 e0 00 01:32:19.200 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 10 e0 00 01:32:19.200 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 08 e0 00 01:32:19.200 READ DMA EXT

Error 14627 [2] occurred at disk power-on lifetime: 14302 hours (595 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 04 00 00 00 03 39 24 e0 00 Error: UNC 4 sectors at LBA = 0x00033924 = 211236

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 00 00 03 39 20 e0 00 01:32:19.600 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 18 e0 00 01:32:19.200 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 10 e0 00 01:32:19.200 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 08 e0 00 01:32:19.200 READ DMA EXT
25 00 00 00 08 00 00 00 03 39 00 e0 00 01:32:19.100 READ DMA EXT

Error 14626 [1] occurred at disk power-on lifetime: 14302 hours (595 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 7c 00 00 00 03 39 24 e0 00 Error: UNC 124 sectors at LBA = 0x00033924 = 211236

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 01 00 00 00 00 03 38 a0 e0 00 01:32:13.500 READ DMA EXT
25 00 00 01 00 00 00 00 03 37 a0 e0 00 01:32:13.400 READ DMA EXT
25 00 00 01 00 00 00 00 03 36 a0 e0 00 01:32:13.400 READ DMA EXT
25 00 00 01 00 00 00 00 03 35 a0 e0 00 01:32:13.400 READ DMA EXT
25 00 00 01 00 00 00 00 03 34 a0 e0 00 01:32:13.300 READ DMA EXT

Error 14625 [0] occurred at disk power-on lifetime: 14301 hours (595 days + 21 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 07 00 00 07 d8 07 d1 e7 00 Error: UNC 7 sectors at LBA = 0x07d807d1 = 131598289

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
25 00 00 00 08 00 00 07 d8 07 d0 e0 00 01:20:02.400 READ DMA EXT
25 00 00 00 3d 00 00 00 33 6e b0 e0 00 01:20:02.400 READ DMA EXT
25 00 00 00 40 00 00 13 06 65 e8 e0 00 01:20:02.400 READ DMA EXT
25 00 00 00 40 00 00 00 33 68 c0 e0 00 01:20:02.400 READ DMA EXT
25 00 00 00 40 00 00 00 33 69 28 e0 00 01:20:02.300 READ DMA EXT

Sysnative Windows Update · Dec 14, 2019

Unfortunately, your drive is very badly damaged and you need to back the data up immediately.

Do not clone this OS, but replace the drive and reinstall Windows from scratch.

gpatel522 · Dec 14, 2019

Thanks for the reply.

The damaged drive is not primary. The OS is on C: which is working fine.
I use the damaged drive as a temporary storage until it gives out completely. Will this drive cause problems with windows update?

Sysnative Windows Update · Dec 14, 2019

Can I get a screenshot of the attributes of the main drive?

It may be wise to disconnect the bad drive while we attempt to upgrade...

gpatel522 · Dec 14, 2019

Here it is. I'll try disconnecting the bad drive and see if update works.

Sysnative Windows Update · Dec 14, 2019

Thanks. Attach CBS.log if it fails again.

gpatel522 · Dec 14, 2019

Again got that error after disconnecting that drive and trying to install the update again.

2019-12 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4530684) -Error 0x800706be

Sysnative Windows Update · Dec 14, 2019

Thanks.

Please do the following:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

gpatel522 · Dec 14, 2019

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-14 17:06:28.985
Microsoft Windows 10 Build 18362 - amd64
Using .zip script file at C:\Users\Gp\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.cat
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.mum

Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\ComponentBasedServicing.LOG1 to C:\WINDOWS\Servicing\Packages\ComponentBasedServicing.LOG1.
Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\ComponentBasedServicing.LOG2 to C:\WINDOWS\Servicing\Packages\ComponentBasedServicing.LOG2.
Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\ComponentBasedServicing{b45fc98d-40f5-11e9-8e36-bc5ff4f040ec}.TM.blf to C:\WINDOWS\Servicing\Packages\ComponentBasedServicing{b45fc98d-40f5-11e9-8e36-bc5ff4f040ec}.TM.blf.
Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\ComponentBasedServicing{b45fc98d-40f5-11e9-8e36-bc5ff4f040ec}.TMContainer00000000000000000001.regtrans-ms to C:\WINDOWS\Servicing\Packages\ComponentBasedServicing{b45fc98d-40f5-11e9-8e36-bc5ff4f040ec}.TMContainer00000000000000000001.regtrans-ms.
Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\ComponentBasedServicing{b45fc98d-40f5-11e9-8e36-bc5ff4f040ec}.TMContainer00000000000000000002.regtrans-ms to C:\WINDOWS\Servicing\Packages\ComponentBasedServicing{b45fc98d-40f5-11e9-8e36-bc5ff4f040ec}.TMContainer00000000000000000002.regtrans-ms.
Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.cat to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.cat.
Successfully copied file C:\Users\Gp\AppData\Local\niemiro\Archive\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.mum to C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.mum.

Successfully restored ownership for C:\WINDOWS\Servicing\Packages
Successfully restored permissions on C:\WINDOWS\Servicing\Packages
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.cat
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.cat
Successfully restored ownership for C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.mum
Successfully restored permissions on C:\WINDOWS\Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package04110~31bf3856ad364e35~amd64~~10.0.18362.1.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2019-12-14 17:08:58.702
Script hash: 61N3WBvFcq+/+hoOuiJ6gohKHrpnfQiRu8Mk4ASePwc=
----------------------EOF-----------------------

Sysnative Windows Update · Dec 14, 2019

Thanks.

Please do the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

gpatel522 · Dec 14, 2019

ok, I got them both saved on Dropbox

CBS.log
Logfile.zip

Sysnative Windows Update · Dec 14, 2019

Please export your CBS folder.

gpatel522 · Dec 14, 2019

sure, here it is

CBS.zip

Sysnative Windows Update · Dec 14, 2019

Was this system cloned?

gpatel522 · Dec 14, 2019

No it was fresh install in August 2019.I can do one again since even my start menu search is not working and I can't seem to find a fix for it. I thought update may have been the problem so trying to find a fix to that first.

Sysnative Windows Update · Dec 14, 2019

This usually happens when there is a drive failing. Have you done a Check Disk on your system drive?

gpatel522 · Dec 14, 2019

There were few errors on c: in checkdisk. It fixed them.

I restarted, deleted everything from C:\Windows\SoftwareDistribution\Download folder and tried to install the update again. But it failed with the same Error 0x800706be

[SOLVED] 2019-12 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4530684) - Install error - 0x800706be

Member

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Member

Attachments

Inactive

Attachments

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Member