2012 R2 - Can't install - undoing changes. RemoveService failed, hr=80248014

W

websterd13

Active member
Joined
Mar 19, 2020
Posts
32
2012R2 Server missing ~40 updates. Have tried downloading updates and manually installing. Have used wsusoffline, same result. Does not matter if I try one update or many. Have tried all steps in the posting instructions, still same result.

SFCFix.exe also found no errors.

I have also used psudo.exe to open a command prompt and changed all permissions on the c:\windows folder to all Everyone:Full. Still did not work.

Your help will be greatly appreciated! This is a production server and I want to keep up with updates. I have created a clone to do testing on to try different things without messing up the production server.

PS 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 did not find any integrity violations.

DISM found errors, but could not fix them. Attaching CBS log and windowsupdate.log files.

Windowsupdate.log shows:

WARNING: ISusInternal::RemoveService failed, hr=80248014
 

Attachments

Hi!

Please start with the following so I can gather more info:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Yes. I figured you guys were busy. But yes, I would love to get a fix for this.

Thanks,

David
 
Great!

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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - 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 SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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.

Then run DISM again and let me know if it completes successfully.
 

Attachments

Thanks again, Everything seemed to work. Here are the results. Please give next steps.

PS C:\Windows\system32> DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.
PS C:\Windows\system32>

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-04-10 08:55:38.506
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\dwadmin\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests

Successfully copied file C:\Users\dwadmin\AppData\Local\niemiro\Archive\Manifests\amd64_02f1921a30bdc2ba502119f136cdd67c_31bf3856ad364e35_6.1.7601.18546_none_dda975fe5baf4a24.manifest to C:\Windows\WinSxS\Manifests\amd64_02f1921a30bdc2ba502119f136cdd67c_31bf3856ad364e35_6.1.7601.18546_none_dda975fe5baf4a24.manifest.
Successfully copied file C:\Users\dwadmin\AppData\Local\niemiro\Archive\Manifests\amd64_8184f3705e57f42a4d65077d6c63eb0e_31bf3856ad364e35_6.1.7601.18270_none_d2b396b6a6a34c03.manifest to C:\Windows\WinSxS\Manifests\amd64_8184f3705e57f42a4d65077d6c63eb0e_31bf3856ad364e35_6.1.7601.18270_none_d2b396b6a6a34c03.manifest.

Successfully restored ownership for C:\Windows\WinSxS\Manifests
Successfully restored permissions on C:\Windows\WinSxS\Manifests
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2020-04-10 08:57:36.849
Script hash: PD4JYhpeSQP3z2Ew2fi00bkWEC8/G/kAMFvTnXuZJYQ=
----------------------EOF-----------------------
 
I tried one manual update and it failed. windows8.1-kb4541505-x64_611fa2250528141948a9f4ec520514ec2737d18b.msu

Attached logs.
 

Attachments

Please do the following:

Step#1 - Export Publishers Key


  1. Click on the Start button type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. 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\WINEVT\Publishers
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file PUB (with no file extension) and save it to your Desktop.


Once done please upload this file via Dropbox or One Drive or SendSpace.
 
OK ran export. The file is very small so just attaching here...just remove the zip extension.
 

Attachments

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Reboot and retry updating again.
 

Attachments

Log from FRST, will try update and post reaults.


Fix result of Farbar Recovery Scan Tool (x64) Version: 13-04-2020
Ran by dwadmin (13-04-2020 09:33:52) Run:2
Running from C:\Temp2
Loaded Profiles: ISCVSvc & dwadmin & ReportServer & MSSQLFDLauncher & SQLSERVERAGENT & MsDtsServer120 & MSSQLSERVER (Available Profiles: hhadmin & ISCVSvc & dwadmin & ReportServer & MSSQLFDLauncher & SQLSERVERAGENT & MsDtsServer120 & MSSQLSERVER)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{2ff3e6b7-cb90-4700-9621-443f389734ed}]
*****************

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{2ff3e6b7-cb90-4700-9621-443f389734ed} => removed successfully

==== End of Fixlog 09:33:52 ====
 
Got to 90% and undid changes. Attaching CBS log. Do you need anything else?

Thanks,

David
 

Attachments

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Please reboot and retry updating. Thank you.
 

Attachments

The frst64 ran, but updates will still not install. Attached CBS log.

Fix result of Farbar Recovery Scan Tool (x64) Version: 15-04-2020
Ran by dwadmin (15-04-2020 09:51:11) Run:3
Running from C:\Temp2
Loaded Profiles: ISCVSvc & dwadmin & ReportServer & MSSQLFDLauncher & SQLSERVERAGENT & MsDtsServer120 & MSSQLSERVER (Available Profiles: hhadmin & ISCVSvc & dwadmin & ReportServer & MSSQLFDLauncher & SQLSERVERAGENT & MsDtsServer120 & MSSQLSERVER)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{a68ca8b7-004f-d7b6-a698-07e2de0f1f5d}]
*****************

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{a68ca8b7-004f-d7b6-a698-07e2de0f1f5d} => removed successfully

==== End of Fixlog 09:51:11 ====
 

Attachments

Please do the following:

Step#1 - Capture Process Monitor BootLog
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install the update just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to a file sharing service of your choice for my review. Examples of services to upload to are Dropbox or OneDrive or SendSpace
 
I have the log in Dropbox, who do I share it with? I can't remember where I saw your dropbox instructions in the forum.

Thanks,

David
 
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