[SOLVED] Windows Server 2012 R2Windows Update issues.

Hi I'm Gary R,


I'm a Security Analyst, and a Windows Update Trainee, and I'd like to help you with your problems.


As a trainee there may be times when my instructions must first be checked by a qualified update expert, before I post them. This will by necessity introduce some delay when/if that occurs, so please be patient.


Can you please do the following for me ...



  • 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, please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
Thanks. Looking things over now, back ASAP.

Going to have to set up a WS2012 R2 VM, so may be a while.
 
You exported your CBS key as a .reg file, I asked you to export it as a Registry Hive file.

Please read my previous instructions again, and send me a copy of your CBS key as a Registry Hive file (need it in that form so I can load it in my VM).
 
No problem. Mistakes happen.

Thanks

Back ASAP.
 
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 SFCFix.exe and save it to your desktop.
  • Download the attachment SFCFix.zip and also 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.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running please try updating
  • If successful please let me know.
  • If unsuccessful ....
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Can you please post me the SFCFix.txt log as well.
 
Im so sorry.. A bit early in the morning here haha.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-03-16 06:42:10.942
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\user\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages

Successfully copied file C:\Users\user\AppData\Local\niemiro\Archive\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.cat to C:\Windows\Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.cat.
Successfully copied file C:\Users\user\AppData\Local\niemiro\Archive\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.mum to C:\Windows\Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.mum.

Successfully restored ownership for C:\Windows\Servicing\Packages
Successfully restored permissions on C:\Windows\Servicing\Packages
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12\Owners.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_307_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2023-03-16 06:43:35.501
Script hash: aHvqZs6CF2NuMaRlYbeLc0szIQXj+U+YYkceSnurF/4=
----------------------EOF-----------------------
 
No problem, it's 6:30am here, so I know what you mean.

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 SFCFixScript.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.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.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Hi!

You want me to try updating again?

CBS is 1 kb :)

________________________________________________________________________________________________________

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-03-16 07:38:45.196
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\user\Desktop\SFCFix (1).zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages

Successfully copied file C:\Users\user\AppData\Local\niemiro\Archive\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.cat to C:\Windows\Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.cat.
Successfully copied file C:\Users\user\AppData\Local\niemiro\Archive\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.mum to C:\Windows\Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.mum.

Successfully restored ownership for C:\Windows\Servicing\Packages
Successfully restored permissions on C:\Windows\Servicing\Packages
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12\Owners.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~0.0.0.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_391_for_KB5009595~31bf3856ad364e35~amd64~~6.3.1.12.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2023-03-16 07:40:07.564
Script hash: MXgo0DaxhzvpLz/buXkYc0kYkTVL5X8z9OnBvog2vQw=
----------------------EOF-----------------------
 
Sorry not to reply faster, been out walking the dogs. Just got back.

Post me your CBS.log and let's see if there's any more errors being flagged before you try updating again.

You've had two errors of a similar type now, different catalog files, but the same error, so I suspect there may be more. For some reason CBS doesn't always list all the errors in one go, but feeds them to you one at a time, so if your latest CBS.log flags another error of the same type, then to speed things up, if I can, I'll need to look at trying to find a different way of finding out how may errors of this type we may have to deal with.
 
OK, no errors being flagged, so please try updating again.

If successful please let me know, if not, then post me your latest CBS.log
 
Going to be out for the next few hours, so probably won't see any reply from you till this afternoon.
 
OK, latest CBS.log is showing similar errors to those we patched earlier (different catalog files of course), so am going to see if I can work out a way to establish what others may need patching.

May take me a while, but I will get back to you ASAP.
 
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