Windows update will be rolled back after reboot

F

FastFerdi

Well-known member
Joined
May 4, 2021
Posts
140
Location
Germany
Hello,

Phil told me to start a new thread, after his awesome support in hunting down and resolve windows update errors on one of my Windows 2012R2 virtual machines.

As I'm still big noob on this topic, I found some bad messages with printer drivers which seemed caused a rollback of successful installed windows updates (rollups) after reboot. I'm glad that he found this remarkable, too.

Please give me a hint which operations and files are necessary to start a new journey.

Cheers
Ferdi
 
Hello Ferdi,

I'm sorry no one else has picked up the challenge of looking into your update problem. If you are happy for me to have another try I will do so.

As usual the starting point will be your CBS folder copied and compressed so that you can upload it via OneDrive or a similar cloud platform.
 
Hello Ferdi,

What is the current status of your system. The logs you posted show that a couple of corruptions were fixed. Have any updates worked recently?
 
Hello Phil,

Windows update shows the latest updates. The download and installation of the updates works well. After the reboot the updates will be uninstalled.

The screenshot says: "The setup of the update could not be completed. The changes are undone."

I've repeated the procedure with the current rollup for february. After the reboot I ran sfc with no errors. Searching for updates shows the february rollup again.

Cheers
Ferdi
 

Attachments

  • CBS.zip
    CBS.zip
    5.8 MB · Views: 2
  • rollback.png
    rollback.png
    17.3 KB · Views: 2
The relevant error messages appear to be the following:
Code: 
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: usbstor.inf, Ranking: 2, Device-Install: 0, Key: 1, Identity: usbstor.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: spaceport.inf, Ranking: 2, Device-Install: 0, Key: 2, Identity: spaceport.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: mshdc.inf, Ranking: 2, Device-Install: 0, Key: 3, Identity: mshdc.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: wvms_pp.inf, Ranking: 2, Device-Install: 0, Key: 4, Identity: wvms_pp.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20237, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: wvid.inf, Ranking: 2, Device-Install: 0, Key: 5, Identity: wvid.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20227, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: sbp2.inf, Ranking: 2, Device-Install: 0, Key: 6, Identity: sbp2.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: sdstor.inf, Ranking: 2, Device-Install: 0, Key: 7, Identity: sdstor.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: prnms002.inf, Ranking: 2, Device-Install: 0, Key: 8, Identity: prnms002.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20194, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: volmgr.inf, Ranking: 2, Device-Install: 0, Key: 9, Identity: volmgr.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20237, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Doqe:   q-stage: Inf: cpu.inf, Ranking: 2, Device-Install: 0, Key: 10, Identity: cpu.inf, Culture=neutral, Type=driverUpdate, Version=6.3.9600.20269, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2022-02-22 23:50:22, Info                  CBS    Perf: Doqe: Staging started.
2022-02-22 23:50:22, Info                  CBS    Doqe: [Forward] Staging driver updates, Count 10
2022-02-22 23:50:22, Info                  CBS            STAGE index: 0, phase: 1, result 0, inf: usbstor.inf
2022-02-22 23:50:22, Info                  CBS            STAGE index: 1, phase: 1, result 0, inf: spaceport.inf
2022-02-22 23:50:22, Info                  CBS            STAGE index: 2, phase: 1, result 0, inf: mshdc.inf
[HI]2022-02-22 23:50:22, Info                  CBS            STAGE index: 3, phase: 1, result 50, inf: wvms_pp.inf
2022-02-22 23:50:22, Info                  CBS    Doqe: Recording result: 0x80070032, for Inf: wvms_pp.inf
2022-02-22 23:50:22, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED][/HI]
2022-02-22 23:50:22, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]
2022-02-22 23:50:22, Info                  CBS    Perf: Doqe: Staging ended.

The wvms_pp.inf is related to the Hyper-V virtual machines and is the VM Switch driver for the network. I am a bit suspicious of the error message that indicates it is not supported since this should be standard on a Server 2012.

The following will examine the sections of the registry that relate to this component and check all copies of the file .

  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. Attach this file into your next post for me to analyse please.
 

Attachments

Last edited:
Thanks Ferdi.

It looks like you may be missing some registry entries. Before fixing these I need to check whether some other registry keys and WinSxS files are present.

Please run the script below using the usual drag and drop method onto SFCFix.exe - it will create a new SFCFix.txt file and also put a wvms_pp.zip file on your desktop. Please attach both of these into your next post.
 

Attachments

Thanks Ferdi.

Please run the attached script as before and this will add the registry entries. Post the txt file so that I can check it.

Afterwards please run SFC /scannow and let me know of it completes successfully. Then reboot the server.
 

Attachments

Now run Dism /Online /Cleanup-Image /RestoreHealth

Afterwards zip up the CBS.log file for me to check.

If all looks good the next stage will be to try the update again.
 
Hello Ferdi,

Sorry for the delay. The latest CBS.log shows some corrupted files that were identified and need fixing.

Code: 
Checking System Update Readiness.

(p)    CSI Payload Corrupt            amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.3.9600.18592_none_b2508e73fd7c833a\isnsui.exe
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.3.9600.18592_none_b2508e73fd7c833a\isnswmi.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.3.9600.18592_none_b2508e73fd7c833a\isnsuid.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.3.9600.18592_none_b2508e73fd7c833a\isnssrv.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.3.9600.18592_none_b2508e73fd7c833a\isnsdll.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_microsoft-windows-isns_service_31bf3856ad364e35_6.3.9600.18592_none_b2508e73fd7c833a\isnscli.exe
Repair failed: Missing replacement payload.

Please use the new SFCFix.zip file attached to carry out the fix by dragging and dropping it onto the SFCFix.exe file on your desktop.
 

Attachments

All looks good! When it is convenient could you please try an update and see if the roll back is still occuring.
 
Hello,

I installed the latest rollup (KB5011564) without any error. After reboot the update was rolled back.

Attached you will find the cbs.log filled while the update was installed.

Inside I found this line:

03-09 19:32:56, Error CBS Doqe: Failed staging driver updates [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]

I did a google search and I found this post on Technet: Technet post

Same windows version and same problem. Maybe a hint?

Cheers
Ferdi
 

Attachments

Thank you for looking through the files and doing the research on the error. It is similar to the one I referenced in post #7.

The setupapi.dev file will be helpful and I will work on this for you over the next few days.
 
Please also run another DISM restorehealth and provide the CBS.log generated after this.

In addition please process the attached script in the usual way and post the SFCFix.txt file which is generated.
 

Attachments

Last edited:
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