2012R2 updates are rolling back

S

sanglyb

Well-known member
Joined
Dec 30, 2022
Posts
52
Hello.
I have a strange problem with our 2012R2 server. Updates installing without any errors, but after reboot they are rolling back everytime.

sfc /scannow is always telling that there are some errors, which can't be fixed.
dism /online /cleanup-image /resotrehealth shows that it fixed some errors, but sfc doesn't think so.
I've tried those commands many times, without any success.

I've attached cbs logs, and ComponentsScanner.txt.

Hope for your help, thx.
 

Attachments

Hello and welcome,

Attach the file C:\Windows\INF\setupapi.dev.log to your next reply.
 
FRST Scan
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  2. Download the attachment fixlist.txt and save it to your desktop.
  3. Right-click on FRST64.exe and select "Run as administrator".
  4. Press the Fix button.
  5. The tool will now process fixlist.txt.
  6. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  8. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Add Missing Package
1. Click the Start button and type cmd in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and press enter.
pnputil -a c:\windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad364e35_6.3.9600.20296_none_fb2fccef62724f72\tsusbhub.inf

4. You will likely receive a prompt that the publisher of the driver cannot be verified. Please install the driver anyway as this message is normal.
5. Provide a screenshot of the result.
 
PeterJ said:
Add Missing Package
1. Click the Start button and type cmd in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and press enter.
pnputil -a c:\windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad364e35_6.3.9600.20296_none_fb2fccef62724f72\tsusbhub.inf

4. You will likely receive a prompt that the publisher of the driver cannot be verified. Please install the driver anyway as this message is normal.
5. Provide a screenshot of the result.
Click to expand...

Hello.
It is always saying that driver is unsigned, and there is no prompt for installing anyway, though I've tried to enable testing mode on the machine, and also I've tried to turn on GPO setting - User configuration - Administrative templates - System - Driver Installation - Code signing for device drivers. I've tried to set it up to both "warn" and "ignore".

Code: 
C:\Windows\system32>pnputil -a c:\windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad364e35_6.3.9600.20296_none_fb2fccef62724f72\tsusbhub.inf
Microsoft PnP Utility

Processing inf :            tsusbhub.inf
Adding the driver package failed : The third-party INF does not contain digital signature information.

Total attempted:              1
Number successfully imported: 0
 
Last edited:
PeterJ said:
Add Missing Package
1. Click the Start button and type cmd in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and press enter.
pnputil -a c:\windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad364e35_6.3.9600.20296_none_fb2fccef62724f72\tsusbhub.inf

4. You will likely receive a prompt that the publisher of the driver cannot be verified. Please install the driver anyway as this message is normal.
5. Provide a screenshot of the result.
Click to expand...
I was able to install the driver, should I do anything else, or I can run dism /online /cleanup-image /restorehealth again?
Code: 
C:\Windows\system32>pnputil -a c:\windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad36
4e35_6.3.9600.20296_none_fb2fccef62724f72\tsusbhub.inf
Microsoft PnP Utility

Processing inf :            tsusbhub.inf
Driver package added successfully.
Published name :            oem27.inf


Total attempted:              1
Number successfully imported: 1
 
or I can run dism /online /cleanup-image /restorehealth again?
Click to expand...
Run the dism command and report the result.
If it fails or fixed something attach the file C:\Windows\Logs\dism\dism.log to your next reply.
 
PeterJ said:
Run the dism command and report the result.
If it fails or fixed something attach the file C:\Windows\Logs\dism\dism.log to your next reply.
Click to expand...
Here is the output of dism and sfc /sannow:
Code: 
C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
 repaired.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

According to fresh cbs.log, may the main cause be in corrupted permissions?
 

Attachments

Weird, the cbs.log shows no error.

Run ComponentsScanner
  • Download
    61f7aba7309a1-ComponentsScanner_Icon.png
    ComponentsScanner and save it on your desktop.
    64bit: https://sysnative.com/apps/componentscollector/ComponentsScanner.exe
    32bit: https://sysnative.com/apps/componentscollector/ComponentsScanner32.exe
  • Double-click ComponentsScanner.exe and click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions. If prompted to perform any repairs, press Y to agree.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Attach that file to your next reply.
 
PeterJ said:
Weird, the cbs.log shows no error.

Run ComponentsScanner
Click to expand...
Here is the requested file.
 

Attachments

PeterJ said:
Weird, the cbs.log shows no error.

Run ComponentsScanner
Click to expand...
I've tried to install an update again, and found in the CBS.LOG after the failure:
Code: 
2023-04-11 21:26:45, Info                  CBS    Perf: Doqe: Install started.
2023-04-11 21:26:45, Info                  CBS    Doqe: [Forward] Installing driver updates, Count 22
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 30, phase: 1, result 0, inf: tpm.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 12, phase: 1, result 0, inf: usbstor.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 14, phase: 1, result 0, inf: prnms003.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 15, phase: 1, result 0, inf: prnms003.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 16, phase: 1, result 0, inf: ntprint.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 17, phase: 1, result 0, inf: ntprint.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 18, phase: 1, result 0, inf: wdmaudio.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 19, phase: 1, result 0, inf: wdma_usb.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 21, phase: 1, result 0, inf: sti.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 22, phase: 1, result 0, inf: tsusbhub.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 23, phase: 1, result 0, inf: wvms_pp.inf
2023-04-11 21:26:45, Info                  CBS            INSTALL index: 24, phase: 1, result 3, inf: wvmbusr.inf
2023-04-11 21:26:45, Info                  CBS    Doqe: Recording result: 0x80070003, for Inf: wvmbusr.inf
2023-04-11 21:26:45, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2023-04-11 21:26:45, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2023-04-11 21:26:45, Info                  CBS    Perf: Doqe: Install ended.
2023-04-11 21:26:45, Info                  CBS    Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2023-04-11 21:26:45, Error                 CBS    Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2023-04-11 21:26:45, Info                  CBS    Startup: Rolling back KTM, because drivers failed.
2023-04-11 21:26:45, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed
2023-04-11 21:26:45, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 0
2023-04-11 21:26:45, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
2023-04-11 21:26:45, Info                  CBS    Setting original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives

Maybe that driver can cause issues?
 

Attachments

I've also run sfcfix to find wvmbusr.inf, here is the output - looks like something is missing.
Should I do something with that driver?
 

Attachments

I think, I was able to fix some drivers, but now there is a problem with tsusbhub.inf on the unregister stage, I would appreciate any ideas.
Code: 
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 30, phase: 1, result 0, inf: tpm.inf
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 12, phase: 1, result 0, inf: usbstor.inf
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 13, phase: 1, result 0, inf: spaceport.inf
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 14, phase: 1, result 0, inf: prnms003.inf
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 15, phase: 1, result 0, inf: prnms003.inf
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 16, phase: 1, result 0, inf: ntprint.inf
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 17, phase: 1, result 0, inf: ntprint.inf
2023-04-13 01:19:26, Info                  CBS    Winlogon: TiCoreOnCreateSession has been called
2023-04-13 01:19:26, Info                  CBS            UNSTAGE index: 18, phase: 1, result 0, inf: wdmaudio.inf
2023-04-13 01:19:27, Info                  CBS            UNSTAGE index: 19, phase: 1, result 0, inf: wdma_usb.inf
2023-04-13 01:19:27, Info                  CBS            UNSTAGE index: 20, phase: 1, result 0, inf: mshdc.inf
2023-04-13 01:19:27, Info                  CBS            UNSTAGE index: 21, phase: 1, result 0, inf: sti.inf
2023-04-13 01:19:27, Info                  CBS            UNSTAGE index: 22, phase: 1, result 50, inf: tsusbhub.inf
2023-04-13 01:19:27, Info                  CBS    DriverUpdateUnstageUpdates failed [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]
2023-04-13 01:19:27, Error                 CBS    Doqe: Failed unstaging driver updates [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]
2023-04-13 01:19:27, Info                  CBS    Perf: Doqe: Unstaging ended.
2023-04-13 01:19:27, Error                 CBS    Failed unstaging drivers (stage rollback), rebooting and trying again [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]
2023-04-13 01:19:27, Info                  CBS    Current global progress. Current: 12, Limit: 25, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback |

Code: 
     sto: {Unstage Driver Package: C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_8e25eb25b4e2bac0\tsusbhub.inf} 01:19:27.029
     sto:      {DRIVERSTORE DELETE BEGIN} 01:19:27.030
     sto:      {DRIVERSTORE DELETE BEGIN: exit(0x00000000)} 01:19:27.030
     idb:      {Unregister Driver Package: C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_8e25eb25b4e2bac0\tsusbhub.inf} 01:19:27.031
!!!  idb:           Cannot unregister published driver package 'tsusbhub.inf_amd64_8e25eb25b4e2bac0'. Error = 0x00000032
!!!  idb:           Failed to unregister driver package 'C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_8e25eb25b4e2bac0\tsusbhub.inf'. Error = 0x00000032
     idb:      {Unregister Driver Package: exit(0x00000032)} 01:19:27.032
     sto:      {DRIVERSTORE DELETE END} 01:19:27.032
     sto:      {DRIVERSTORE DELETE END: exit(0x00000032)} 01:19:27.032
!!!  sto:      Failed to delete driver package from Driver Store. Error = 0x00000032
     sto: {Unstage Driver Package: exit(0x00000032)} 01:19:27.034
!!!  sto: Failed to unstage all driver updates. Error = 0x00000032

Also I attached fresh tsusbhub.inf scan result, in case if it can be useful.
 

Attachments

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

PeterJ said:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
Click to expand...
SFCFix worked without errors, but unfortunately, the situation didn't change - same error - Failed to unregister driver package.
 

Attachments

Add Missing Package
1. Click the Start button and type cmd in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and press enter.
pnputil -a C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.19432_none_53d7bffec532f380\wvms_pp.inf

4. You will likely receive a prompt that the publisher of the driver cannot be verified. Please install the driver anyway as this message is normal.
 
PeterJ said:
Add Missing Package
1. Click the Start button and type cmd in the search box.
2. Right-click on the cmd that comes up and select Run as administrator.
3. Once you are at the command prompt, copy/paste the following line and press enter.
pnputil -a C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.19432_none_53d7bffec532f380\wvms_pp.inf

4. You will likely receive a prompt that the publisher of the driver cannot be verified. Please install the driver anyway as this message is normal.
Click to expand...
Thank you very much!!! With your help, and after reading other similar posts on this forum, I was able to fix that and several other drivers in the store, and now updates finally installed, at least there were no problems with january and february CUs. I'm not sure that in future there will not be problems, but for now at least, it works =) The only one strange thing is that sfc /scannow still showing, that it couldn't fix some problems, though there are no direct errors in cbs.log.
 
Great.

The only one strange thing is that sfc /scannow still showing, that it couldn't fix some problems, though there are no direct errors in cbs.log.
Click to expand...
Please attach the file so we can have a look too.
 
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