P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 5, 2019 #121 Follow the instructions below. If anything is unclear please ask first. Open compmgmt.msc Navigate on the left side to Disk Management Right-click the recovery / system partition and select change drive letters and paths Map a drive letter Open windows explorer to browse that drive Delete unneeded files to free up space. Remove the drive letter by using compmgmt.msc again. Reboot the machine. Tell me if the above went successful or not.
Follow the instructions below. If anything is unclear please ask first. Open compmgmt.msc Navigate on the left side to Disk Management Right-click the recovery / system partition and select change drive letters and paths Map a drive letter Open windows explorer to browse that drive Delete unneeded files to free up space. Remove the drive letter by using compmgmt.msc again. Reboot the machine. Tell me if the above went successful or not.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 8, 2019 #122 Sorry Peter, but I am confused. What Partition are you referring to? I would assume the H: System Reserved but assumptions can be costly. I did remove an image file which gave me 33mb of space. What other files should I remove, before I remove the H: drive letter?
Sorry Peter, but I am confused. What Partition are you referring to? I would assume the H: System Reserved but assumptions can be costly. I did remove an image file which gave me 33mb of space. What other files should I remove, before I remove the H: drive letter?
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 8, 2019 #123 Drive H: is indeed the right one. Please do the following so we can see the result. Right-click on FRST64.exe and select "Run as administrator". Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area. Press the Scan button. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop) Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
Drive H: is indeed the right one. Please do the following so we can see the result. Right-click on FRST64.exe and select "Run as administrator". Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area. Press the Scan button. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop) Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 8, 2019 #124 I ran and will attach, of course. When I was closing up FARBAR there we a note from Windows that there was a problem which it will look into. It never does. It was the same message I get when closing Quicken. Attachments FRST.txt 67.2 KB · Views: 0 Addition.txt 30.2 KB · Views: 2
I ran and will attach, of course. When I was closing up FARBAR there we a note from Windows that there was a problem which it will look into. It never does. It was the same message I get when closing Quicken.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 8, 2019 #125 Check Windows Update again and report the result. If it fails attach the zipped cbs.log to your next reply.
Check Windows Update again and report the result. If it fails attach the zipped cbs.log to your next reply.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 8, 2019 #126 Windows Update is shut down because it was automatically executing the updates that are now in Pending. Is it okay to try KB4474419 even though it is in PENDING state in Windows Update History. Also, Windows is somehow automatically installing the Windows Security Essential updates. The last listed is today with Definitions 1.297.672.0.
Windows Update is shut down because it was automatically executing the updates that are now in Pending. Is it okay to try KB4474419 even though it is in PENDING state in Windows Update History. Also, Windows is somehow automatically installing the Windows Security Essential updates. The last listed is today with Definitions 1.297.672.0.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 9, 2019 #127 Installing Windows Security Essential updates is no problem at all. Restart the machine. Let Windows Update do its job and report the state when done.
Installing Windows Security Essential updates is no problem at all. Restart the machine. Let Windows Update do its job and report the state when done.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 9, 2019 #128 deleted, posted in the wrong thread.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 9, 2019 #129 Windows Update in Control Panel had KB890830 and KB4507420 and a Monthly Rollup which I Hid. The 2 KB files installed okay. There was NO CBS.log file created. When I went to shutdown I looked at CBS.log and sure enough it had information. Attachments CBS.log 860.6 KB · Views: 1 Last edited: Jul 9, 2019
Windows Update in Control Panel had KB890830 and KB4507420 and a Monthly Rollup which I Hid. The 2 KB files installed okay. There was NO CBS.log file created. When I went to shutdown I looked at CBS.log and sure enough it had information.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 10, 2019 #130 Step 1: Remove Update Manually Click on the Start button and in the search box, type Command Prompt. When you see Command Prompt on the list, right-click on it and select Run as administrator. When command prompt opens, copy and paste the following commands into it, then press enter after each. wusa /uninstall /KB:3133977 wusa /uninstall /KB:4474419 Step 2: FRST Registry Search Click your Start button and choose Control Panel. In the upper right corner ensure the View by: is set to Category. Select the Programs group. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open. Right-click on the file FRST64.exe and choose Run as administrator. Copy and paste KB3133977;KB4474419 into the Search box and click the Search Registry button. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply. You may close any remaining open windows now.
Step 1: Remove Update Manually Click on the Start button and in the search box, type Command Prompt. When you see Command Prompt on the list, right-click on it and select Run as administrator. When command prompt opens, copy and paste the following commands into it, then press enter after each. wusa /uninstall /KB:3133977 wusa /uninstall /KB:4474419 Step 2: FRST Registry Search Click your Start button and choose Control Panel. In the upper right corner ensure the View by: is set to Category. Select the Programs group. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open. Right-click on the file FRST64.exe and choose Run as administrator. Copy and paste KB3133977;KB4474419 into the Search box and click the Search Registry button. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply. You may close any remaining open windows now.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 10, 2019 #131 Step 1 found nothing. Step 2 found a lot of both Attachments SearchReg.txt 665.9 KB · Views: 2
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 10, 2019 #132 Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Step 2: Check Windows Update but do not install anything. Please report which updates are available. Attachments fixlist.txt 616.1 KB · Views: 11
Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. 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. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Post the logfile Fixlog.txt as attachment in your next reply. Step 2: Check Windows Update but do not install anything. Please report which updates are available.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 10, 2019 #133 At the moment there are NO new Updates to be installed. This may take a while if Windows finds it needs some. For now here is the Fixlog.txt The 3 in Pending are still there. I will do a Restart and see if that causes any action. No activity in Windows Update. Attachments Fixlog.txt 1.2 MB · Views: 3 Last edited: Jul 10, 2019
At the moment there are NO new Updates to be installed. This may take a while if Windows finds it needs some. For now here is the Fixlog.txt The 3 in Pending are still there. I will do a Restart and see if that causes any action. No activity in Windows Update.
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 11, 2019 #134 I have attached a file of Updates that over time were downloaded directly from Microsoft Update Catalog. I have checked and none of them show installed. Some are Pending and one Failed according to VIEW UPDATE HISTORY. I still have the message "Windows is up to date" Attachments UPDATES.txt 574 bytes · Views: 1
I have attached a file of Updates that over time were downloaded directly from Microsoft Update Catalog. I have checked and none of them show installed. Some are Pending and one Failed according to VIEW UPDATE HISTORY. I still have the message "Windows is up to date"
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 12, 2019 #135 I still have the message "Windows is up to date" Click to expand... Did the July 2019 updates install successfully ?
I still have the message "Windows is up to date" Click to expand... Did the July 2019 updates install successfully ?
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 12, 2019 #136 Nothing has shown up to be installed since the 2 I installed on 7/9/2019 #129. I just looked and the same message Windows is Up to Date. View History does show 2 more Microsoft Security Essential updates installed without my knowledge, KB2310138 on 7/10 and 7/12. I would like to try KB4474419 again as not having it could stop everything else according to Microsoft.
Nothing has shown up to be installed since the 2 I installed on 7/9/2019 #129. I just looked and the same message Windows is Up to Date. View History does show 2 more Microsoft Security Essential updates installed without my knowledge, KB2310138 on 7/10 and 7/12. I would like to try KB4474419 again as not having it could stop everything else according to Microsoft.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 13, 2019 #137 Install Update with DISM Download the update MSU here: http://download.windowsupdate.com/c..._6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu Copy the MSU file to a convenient location (such as C:\temp). Click on the Start button and in the search box, type Command Prompt When you see Command Prompt on the list, right-click on it and select Run as administrator When command prompt opens, copy and paste the following commands into it, press enter after each cd C:\temp replace C:\temp with your path if different expand windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu -f:* C:\temp DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4474419-x64 You should receive the message: The operation completed successfully. Make sure to allow the computer to restart if prompted. If you receive any other message: Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied. Paste (Ctrl+V) it into your next post. Zip and attach C:\Windows\Logs\CBS\CBS.log
Install Update with DISM Download the update MSU here: http://download.windowsupdate.com/c..._6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu Copy the MSU file to a convenient location (such as C:\temp). Click on the Start button and in the search box, type Command Prompt When you see Command Prompt on the list, right-click on it and select Run as administrator When command prompt opens, copy and paste the following commands into it, press enter after each cd C:\temp replace C:\temp with your path if different expand windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu -f:* C:\temp DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4474419-x64 You should receive the message: The operation completed successfully. Make sure to allow the computer to restart if prompted. If you receive any other message: Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied. Paste (Ctrl+V) it into your next post. Zip and attach C:\Windows\Logs\CBS\CBS.log
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 15, 2019 #138 The expand worked. C:/Temp now has Windows6.1-KB4474419-x64.cab Windows6.1-KB4474419-x64.xml windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu Windows6.1-KB4474419-x64-pkgProperties.txt WSUSSCAN.cab COMMAND PROMPT INFORMATION Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>cd C:\temp C:\Temp>expand windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9 .msu -f:* C:\temp Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Adding C:\temp\WSUSSCAN.cab to Extraction Queue Adding C:\temp\Windows6.1-KB4474419-x64.cab to Extraction Queue Adding C:\temp\Windows6.1-KB4474419-x64-pkgProperties.txt to Extraction Queue Adding C:\temp\Windows6.1-KB4474419-x64.xml to Extraction Queue Expanding Files .... Expanding Files Complete ... 4 files total. C:\Temp>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4474419- x64 Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.18489 An error occurred trying to open - C:\temp\windows6.1-kb4474419-x64 Error: 0x800 70003 Error: 3 The system cannot find the path specified. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Temp> Attachments CBS.zip 372.2 KB · Views: 0
The expand worked. C:/Temp now has Windows6.1-KB4474419-x64.cab Windows6.1-KB4474419-x64.xml windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu Windows6.1-KB4474419-x64-pkgProperties.txt WSUSSCAN.cab COMMAND PROMPT INFORMATION Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>cd C:\temp C:\Temp>expand windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9 .msu -f:* C:\temp Microsoft (R) File Expansion Utility Version 6.1.7600.16385 Copyright (c) Microsoft Corporation. All rights reserved. Adding C:\temp\WSUSSCAN.cab to Extraction Queue Adding C:\temp\Windows6.1-KB4474419-x64.cab to Extraction Queue Adding C:\temp\Windows6.1-KB4474419-x64-pkgProperties.txt to Extraction Queue Adding C:\temp\Windows6.1-KB4474419-x64.xml to Extraction Queue Expanding Files .... Expanding Files Complete ... 4 files total. C:\Temp>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4474419- x64 Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.18489 An error occurred trying to open - C:\temp\windows6.1-kb4474419-x64 Error: 0x800 70003 Error: 3 The system cannot find the path specified. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log C:\Temp>
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 13,892 Jul 15, 2019 #139 Sorry, the DISM command was incorrect. It should be DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4474419-x64.cab
Sorry, the DISM command was incorrect. It should be DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4474419-x64.cab
C ChuckR Well-known member Joined Nov 24, 2016 Posts 301 Jul 15, 2019 #140 IT WORKED. kb4474419 installed. With all we did it is hard to pinpoint what was corrected. Should I try other Updates, such as kb4499175 which failed earlier? Thanks
IT WORKED. kb4474419 installed. With all we did it is hard to pinpoint what was corrected. Should I try other Updates, such as kb4499175 which failed earlier? Thanks