A Alex2801 Member Joined Feb 25, 2019 Posts 18 Jul 18, 2019 #1 Hi sysnative team, i tried to install the monthly updates on our terminalservers, on KB4507449 occured the error 80242016. After rebooting the update was still marked as requiered in wsus for the machine, no listing of the Update in the installed updates section. The update timeline shows the error. After that i tried to inejct the CAB of KB4507449 via dism /online, it worked without complains. Since then the update was no more marked as requiered in wsus, but it is still not listed in the installed updates. So i Did SFC which said all is compliant, after that i ran surt which found arround 450 errors and fixed some of them. After that i ran sfcfix, all the logs are attached. Is there any work to do for me? Logs: cbslog.zip Thank you in advance, Alex
Hi sysnative team, i tried to install the monthly updates on our terminalservers, on KB4507449 occured the error 80242016. After rebooting the update was still marked as requiered in wsus for the machine, no listing of the Update in the installed updates section. The update timeline shows the error. After that i tried to inejct the CAB of KB4507449 via dism /online, it worked without complains. Since then the update was no more marked as requiered in wsus, but it is still not listed in the installed updates. So i Did SFC which said all is compliant, after that i ran surt which found arround 450 errors and fixed some of them. After that i ran sfcfix, all the logs are attached. Is there any work to do for me? Logs: cbslog.zip Thank you in advance, Alex
A Alex2801 Member Joined Feb 25, 2019 Posts 18 Jul 30, 2019 #2 Hey, do anyone have any advice for me? Thanks again, Alex
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 2, 2019 #3 Hi! Apologies for the delay. Are you still in need of assistance?
A Alex2801 Member Joined Feb 25, 2019 Posts 18 Aug 5, 2019 #4 Hi @softwaremaniac, thanks for your reply. yes, we still need assistance, we dont want to publish a machine which is perhabs broken. Thank you! Alex
Hi @softwaremaniac, thanks for your reply. yes, we still need assistance, we dont want to publish a machine which is perhabs broken. Thank you! Alex
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 5, 2019 #5 Hi! Is this a virtual machine or a physical one?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 6, 2019 #7 Okay, this is a fairly complex issue and will take several iterations to fix. Please be patient.
A Alex2801 Member Joined Feb 25, 2019 Posts 18 Aug 21, 2019 #8 hi @softwaremaniac are there any news? :/ Thanks, Alex
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 21, 2019 #9 Hi! Please do the following: Retrieve Components Hive 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file. 2. Please copy this file to your desktop. Note: If you receive an error that this file is in-use, simply reboot your computer and try again. 3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop. 4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
Hi! Please do the following: Retrieve Components Hive 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file. 2. Please copy this file to your desktop. Note: If you receive an error that this file is in-use, simply reboot your computer and try again. 3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop. 4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
A Alex2801 Member Joined Feb 25, 2019 Posts 18 Aug 22, 2019 #10 Hi, thanks for your answer, i couldnt copy it with windows even as system and with multiple restarts, but ShadowSpawn worked for me, so the components file is attached. Drive Thank you! Alex
Hi, thanks for your answer, i couldnt copy it with windows even as system and with multiple restarts, but ShadowSpawn worked for me, so the components file is attached. Drive Thank you! Alex
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Aug 24, 2019 #11 Hi! 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 6.3 KB · Views: 1
Hi! 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.