R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 17, 2020 #1 Dear Forum, on a Windows 2019 Server I get the Error 0x800f0982 while installing KB4534273. I did all the "normal" Stuff like the https://support.microsoft.com/de-de/help/4027322/windows-update-troubleshooter and the other tools from the ms tech forum. But it does not work. Can somebody give me a hint how to diag the problem? Best regards, Rock Attachments CBS.zip 1.2 MB · Views: 6
Dear Forum, on a Windows 2019 Server I get the Error 0x800f0982 while installing KB4534273. I did all the "normal" Stuff like the https://support.microsoft.com/de-de/help/4027322/windows-update-troubleshooter and the other tools from the ms tech forum. But it does not work. Can somebody give me a hint how to diag the problem? Best regards, Rock
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 18, 2020 #2 here is an Update of the cbs log with only the Update failing. (Short Version) Attachments CBS.zip 10.6 KB · Views: 2
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 20, 2020 #3 I deinstalled all asian Language packs, but the error stays the same.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 23, 2020 #4 Hello and welcome! Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
Hello and welcome! Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 24, 2020 #5 Dear Softwaremaniac, here are the files: CBS.7z and 1 more file Best regards and thank you a lot, David
Dear Softwaremaniac, here are the files: CBS.7z and 1 more file Best regards and thank you a lot, David
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 24, 2020 #6 Thanks. 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 fixlist.txt 2.4 KB · Views: 10
Thanks. 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.
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 25, 2020 #7 Dear Softwaremaniac, here is the log. Best regards, David Attachments Fixlog.txt 3.4 KB · Views: 5
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 25, 2020 #8 Error changed from 0x800f0982 to 0x80246007 and back again to 0x800f0982.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 25, 2020 #9 Hi! Please do the following again: Error 0x800f0982 with KB4534273 in Windows Server 2019
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 25, 2020 #10 Dear Softwaremaniac, here are the new files: CBS.log and 1 more file Thank you again! David
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 25, 2020 #11 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. Afterwards, retry updates with ProcMon. Attachments fixlist.txt 2.4 KB · Views: 9
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. Afterwards, retry updates with ProcMon.
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 25, 2020 #12 Sorry for the delay. Here is the new log: CBS.log and 1 more file
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 25, 2020 #13 Can I see the fixlog?
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 25, 2020 #14 Had to rerun the fix to rebuild the fixlog again. I cleaned ist up, sorry. Attachments Fixlog.txt 3.4 KB · Views: 4
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 25, 2020 #15 OK, run ProcMon again now.
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 26, 2020 #16 CBS.log and 1 more file here you go.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 26, 2020 #17 Thanks. 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. Afterwards, run ProcMon again and try updates. Attachments fixlist.txt 2.8 KB · Views: 7
Thanks. 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. Afterwards, run ProcMon again and try updates.
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 27, 2020 #18 Hi Softwaremaniac, here are the new logfiles: CBS.log and 1 more file
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 27, 2020 #19 I need to see the fixlog as well. Thanks.
R rockwilder Member Joined Jan 17, 2020 Posts 15 Jan 27, 2020 #20 Here is the fixlog: Attachments Fixlog.txt 3.8 KB · Views: 8