[SOLVED] Cannot install any updates, stuck on Windows 10 1703 Build 15063.726

That's not a fail. Fail is when you get an error.

Please list all the hardware present in the machine.

Please try the following:

Download the following file.
Create a new folder on your Desktop.
Extract the file you've downloaded to a new folder on your Desktop you've created in the previous step.
Right-click ResetWUEng.cmd file and select Run as Administrator.
A windows will appear prompting you if you want to continue with the process. Please press Y.
Another menu will appear. Press 2: Reset Windows Update Components.
Verify that you have selected number 2 and hit Enter.
Wait until the process is complete.
You should see the message: The operation completed successfully.
Press any key to continue. . .

Close the window and reboot.

Afterwards, check for updates and let me know which show up.
 
The Hardware is:

ASUS Desktop with:

  • Intel i3-4130 @ 3.40GHz
  • H81M-E motherboard Bios 3601.
  • Samsung EVO 850 128GB SSD
  • Inbuilt Intel Graphics 4400
  • VGA Graphics cord to an LG Monitor
  • DVD Writer
Attached to it via USB are:
  • Wired Mouse
  • Wired Keyboard
  • Printer - Brother HL-3150CDN
  • Scanner - Canoscan LIDE 220
  • Wifi Dongle - n/b/g

I have tried unplugging all but mouse and keyboard and check for Windows Updates.

Ran the ResetWUEng.cmd file and it completed successfully, then rebooted once (or could be twice) and check for Windows Updates, which took quite a while.

The machine then listed an update for Windows Defender (I think), then checked for updates again and said something like "Your device is at risk because it's out of date and missing important security and quality updates. Let's get you back on track so Windows can run more securely. Select this button to get going:", and the button is "Check for Updates". I pressed this and it returned back to the same screen.
 
Time to retry this:

1. Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
2. Accept the License Agreement
3. Download the ISO file to your desktop.
4. Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours.
 
I got the following result from an in place install from a downloaded DVD.

"We couldn't install Windows 10
We've set your PC back to the way it was right before you started installing Windows 10.

0x8007001F - 0x20006
The installation failed in the SAFE_OS phase with an error during the REPLICATE_OC operation"

I have attached:
 
Are you using Broadcom Wireless drivers by any chance?

Please navigate to the following key and take a screenshot of every value there along with its data:

HKLM\SYSTEM\CurrentControlSet\Control\Cryptography\Providers
 
Please physically disconnect the dongle and any other peripheral devices except keyboard/mouse and monitor and make sure you disable wifi in your BIOS/UEFI if present and try upgrading from the ISO again.
 
Something is bugging me here. Please do the following so I can gather more info:

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.


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

Attachments

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-09-03 12:59:10.564
Microsoft Windows 10 Build 15063 - amd64
Using .txt script file at C:\Users\Tony\Downloads\SFCFixScript.txt [0]








FileScan::
[0: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wrpint.dll
File is untraceable.
 Found: GV8IdlxMm18/V/IFtUYyUbilvwXo6P7rrgJjCuR8Kek=
 Version number not available.
Trace not available.






[1: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_4272b41975286995\wrpint.dll
File is untraceable.
 Found: GV8IdlxMm18/V/IFtUYyUbilvwXo6P7rrgJjCuR8Kek=
 Version number not available.
Trace not available.






[2: 1] C:\Users\Tony\Downloads\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.724_none_9e8a868b2d8a538d\wrpint.dll
File is untraceable.
 Found: UL1i6we4hyYvovsVfFoU7dLA++9nIjXCY9Jzu1SFsJI=
 Found: 10.0.15063.0
Trace not available.






[3: 1] C:\SFCFix\Backups\C\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.724_none_9e8a868b2d8a538d\wrpint.dll
File is untraceable.
 Found: UL1i6we4hyYvovsVfFoU7dLA++9nIjXCY9Jzu1SFsJI=
 Found: 10.0.15063.0
Trace not available.






[4: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.724_none_426beb07752ce257\wrpint.dll
File is untraceable.
 Found: ZCdgfXhTWoBRUQ6F8ZHydpkaNVPznFp6z0VDFaGvZ9M=
 Found: 10.0.15063.0
Trace not available.






[5: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.724_none_9e8a868b2d8a538d\wrpint.dll
File is untraceable.
 Found: UL1i6we4hyYvovsVfFoU7dLA++9nIjXCY9Jzu1SFsJI=
 Found: 10.0.15063.0
Trace not available.






[6: 1] C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.0_none_be549efe47bbc296\wrpint.dll
File is untraceable.
 Found: 7fD/ciWugjmjjcV9IupgzcW4MT945pn9RvUeOqKLaEg=
 Version number not available.
Trace not available.






[7: 1] C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.0_none_1a733a82001933cc\wrpint.dll
File is untraceable.
 Found: 7fD/ciWugjmjjcV9IupgzcW4MT945pn9RvUeOqKLaEg=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 20 datablocks.
Finish time: 2018-09-03 12:59:12.960
Script hash: 8xHiICBNDJ3AF6wvHLs+gMoT4tkAQPky3ZNP1qLYDJw=
----------------------EOF-----------------------
 
Thanks for the info. Please do the following.

1. Click your Start button and type cmd in the search box. Right-click on cmd from the search results and select Run as administrator. Answer Yes if the UAC prompt comes up.
2. Copy/Paste the following in to the command-prompt window and hit enter.
wmic qfe list brief /format:texttablewsys > "%USERPROFILE%\desktop\hotfix.txt"

3. This will create a file on your desktop named hotfix.txt. Please attach this to your next reply.
 
Wmic seems to be asleep or something :)

Code: 
C:\WINDOWS\system32>wmic qfe list brief /format:texttablewsys > "%USERPROFILE%\desktop\hotfix.txt"
No Instance(s) Available.


C:\WINDOWS\system32>
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the wmic command just like you have in the past.
3. Stop Process Monitor as soon as you get No Instance(s) Available. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log
 
Step#1 - Export registry as hive



  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to SendSpace and just provide the link here.
 
Thanks.

Please do the following as well:

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install the servicing stack update just like you have in the past.
3. Stop Process Monitor as soon as you get the error. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log
 
I have made some progress which I think identifies the problem with not being able to install updates, my supposition is the issue is:

  1. c:\windows\winsxs has (correctly) many packages installed
  2. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages has hardly any packages installed

To test this I took ownership of HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages and then created these keys:

Firstly a parent package to indicate this is Windows Home that is installed
Code: 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-CoreEdition~31bf3856ad364e35~amd64~~10.0.15063.0]
"CurrentState"=dword:00000070

Then a single (there should actually be 100, but for the purposes of experimentation I did one) an actual package to be updated
Code: 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-ServicingStack-Base-Package~31bf3856ad364e35~amd64~en-US~10.0.15063.0]
"CurrentState"=dword:00000070

This then deals partially with the many absent packages in CBS.log. I checked names against CBS.log from prior to the problem occurring in November 2017.

Subsequently it allows KB4132649 (Servicing Stack) to at least installed via a downloaded WSU file although it is only partial as it only updates Package 4 and 45 of about 100.
Similarly then KB4088891 (March 22, 2018—KB4088891 (OS Build 15063.994) for Windows 10, version 1703) was then downloaded and installed by Windows update but only applied Package 4554 and 4555 of many thousand.
These updates are of course only partial.

I then tried to proceed further with an inplace upgrade to 1803 but this failed as in the past.

So I am on the right path that the SOFTWARE Hive has severe problems? If then, how do I restore the thousands of missing registry keys?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top