Windows Update Crashes PC - Please Help !

Remove Update Manually
1. Click on the Start button and in the search box, type Command Prompt.
2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
3. When command prompt opens, copy and paste the following command into it, then press enter.
wusa /uninstall /KB:3022345

4. Let me know if it says it was successful or if there are any errors.
 
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. 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.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Here is the log.

Fix result of Farbar Recovery Scan Tool (x86) Version: 01-01-2019
Ran by Admin (08-01-2019 09:48:37) Run:6
Running from C:\Users\Public\Desktop\Transfer
Loaded Profiles: Admin (Available Profiles: aguser & AAgent User & AAgent User 2 & Admin)
Boot Mode: Normal


==============================================


fixlist content:
*****************
cmd: dir C:\Windows\winsxs\x86_usb.inf.resources_31bf3856ad364e35_6.1.7601.24138_en-us_2b9d7c3687d0cba0 /s
cmd: dir c:\Windows\winsxs\x86_usbport.inf.resources_31bf3856ad364e35_6.1.7601.24138_en-us_f08bddda1e43af71 /s




*****************




========= dir C:\Windows\winsxs\x86_usb.inf.resources_31bf3856ad364e35_6.1.7601.24138_en-us_2b9d7c3687d0cba0 /s =========


Volume in drive C has no label.
Volume Serial Number is 02FC-93E2


Directory of C:\Windows\winsxs\x86_usb.inf.resources_31bf3856ad364e35_6.1.7601.24138_en-us_2b9d7c3687d0cba0


03/10/2018 12:46 PM <DIR> .
03/10/2018 12:46 PM <DIR> ..
13/07/2009 06:01 PM 13,962 usb.inf_loc
02/05/2018 07:52 AM 11,776 usbhub.sys.mui
2 File(s) 25,738 bytes


Total Files Listed:
2 File(s) 25,738 bytes
2 Dir(s) 47,711,006,720 bytes free


========= End of CMD: =========




========= dir c:\Windows\winsxs\x86_usbport.inf.resources_31bf3856ad364e35_6.1.7601.24138_en-us_f08bddda1e43af71 /s =========


Volume in drive C has no label.
Volume Serial Number is 02FC-93E2


Directory of c:\Windows\winsxs\x86_usbport.inf.resources_31bf3856ad364e35_6.1.7601.24138_en-us_f08bddda1e43af71


07/01/2019 09:09 AM <DIR> .
07/01/2019 09:09 AM <DIR> ..
02/05/2018 07:52 AM 3,072 usbehci.sys.mui
02/05/2018 07:52 AM 11,776 usbhub.sys.mui
20/11/2010 04:10 AM 24,236 usbport.inf_loc
02/05/2018 07:51 AM 24,576 usbport.sys.mui
4 File(s) 63,660 bytes


Total Files Listed:
4 File(s) 63,660 bytes
2 Dir(s) 47,710,957,568 bytes free


========= End of CMD: =========




==== End of Fixlog 09:48:37 ====
 
Here you go :)

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.
 
Looks good.
Check Windows Update again and report the result.
If it fails, run sfc /scannow again and attach the zipped cbs.log to your next reply.
 
Here you go.

It failed to install just the Security Updates again. SFC Scan reported No Errors :)

Capture.JPG
 

Attachments

Post the logfile C:\Windows\WindowsUpdate.log as attachment in your next reply.
Note: if the file is too big to upload to your next reply please upload via a service such as Filedropper or One Drive or SendSpace and just provide the download link.
 
Check for Windows Updates and take a screenshot of the available updates. Read this on how to take a screenshot.
Upload the image file to a file-sharing site such as Filedropper or SendSpace and post the downloadlink.
 
Hi Peter,

Just the one. It was showing up 2018-12 Security Monthly as pending before (last month) & now its showing as 2019-01 is the only one pending. Although they both crashes the PC .

Capture.JPG
 
And , just so you know. Even if I download the security updates manually & use WUSA to install , it doesn't work :( It would say, Installed Successfully & needed a reboot. Will boot in to the point where Blue screen appears with please wait screen & then crash to "Advanced Boot Configuration" . I do see others in this forum & many other forums are having tough time installing Security updates. Typical MS !
 
Step 1:
  1. Click your start button and type cmd in the search box.
  2. Right-click on cmd that comes up in the search results and select Run as administrator. Answer Yes to the UAC prompt if it appears.
  3. Copy/Paste the following into the command-prompt window and hit enter.
    reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /s > 1.txt && notepad 1.txt

  4. Notepad will open showing the WU info. Copy and paste this into your next reply.

Step 2:
Download and install BlueScreenView.
  1. When the installation is finished BlueScreenView will start automatically.
  2. Select the most recent file in the list Dump File and press the keys Ctrl+A.
  3. Click File - Save Selected Items.
  4. Save the file on your desktop.
  5. Upload this file to a file-sharing site such as Filedropper or One Drive or SendSpace and just provide the download link.
 
Here is the Log :)


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
SusClientId REG_SZ 907d8790-6cf2-48d5-83dc-5fff64a501fa
SusClientIdValidation REG_BINARY 06022801280E2000200020002000200020002000200020002000200020005700320041005400390051005600420006FC4DD43968B5200020002000200020002000200020002000200020002000200020002000200020002000200020004D004A0035003700300052004D00
LastRestorePointSetTime REG_SZ 2019-01-10 20:06:43


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
NextDetectionTime REG_SZ 2019-01-11 15:17:18
NextSqmReportTime REG_SZ 2019-01-11 18:38:46
NextFeaturedUpdatesNotificationTime REG_SZ 2018-10-02 22:56:24
FeaturedUpdatesNotificationSeqNum REG_DWORD 0x1043
FeaturedUpdatesNotificationSeqNumGenTime REG_SZ 2018-12-28 19:14:15
ScheduledInstallDate REG_SZ 2019-01-11 11:00:00
BalloonTime REG_SZ 2019-01-09 18:39:02
BalloonType REG_DWORD 0x8
ActionCenterNotificationCount REG_DWORD 0x4
ActionCenterLastPossibleRestartNotification REG_SZ 2018-10-04 10:00:00
LastRestoreId REG_SZ {3359D5B5-BE91-413C-9203-D517DE682170}


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Detect
LastSuccessTime REG_SZ 2019-01-10 20:16:35
LastError REG_DWORD 0x0


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Download
LastSuccessTime REG_SZ 2019-01-10 11:03:27
LastError REG_DWORD 0x0


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Install
LastSuccessTime REG_SZ 2019-01-10 11:00:51
LastError REG_DWORD 0x80070002


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\UAS
UpdateCount REG_DWORD 0x1


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting
BatchFlushAge REG_DWORD 0x1fc
SamplingValue2 REG_DWORD 0x30a


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\RebootWatch


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending
ValidatedPreWsus3RegistrationRequests REG_DWORD 0x1


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup
SelfUpdateStatus REG_DWORD 0x0
SelfupdateUnmanaged REG_DWORD 0x0
 
And there are NO Dump Files as I never had BSOD :)
Click to expand...
I thought so because you said:
Installed Successfully & needed a reboot. Will boot in to the point where Blue screen appears...
Click to expand...


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.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. 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.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Check Windows Update again and report the result.
 

Attachments

Hi Peter,

So it crashed again. Seems like the "Last Error" number got changed :O



HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
SusClientId REG_SZ 907d8790-6cf2-48d5-83dc-5fff64a501fa
SusClientIdValidation REG_BINARY 06022801280E2000200020002000200020002000200020002000200020005700320041005400390051005600420006FC4DD43968B5200020002000200020002000200020002000200020002000200020002000200020002000200020004D004A0035003700300052004D00
LastRestorePointSetTime REG_SZ 2019-01-10 23:38:08


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
NextDetectionTime REG_SZ 2019-01-11 20:02:49
NextSqmReportTime REG_SZ 2019-01-11 18:38:46
NextFeaturedUpdatesNotificationTime REG_SZ 2018-10-02 22:56:24
FeaturedUpdatesNotificationSeqNum REG_DWORD 0x1043
FeaturedUpdatesNotificationSeqNumGenTime REG_SZ 2018-12-28 19:14:15
ScheduledInstallDate REG_SZ 2019-01-11 11:00:00
BalloonTime REG_SZ 2019-01-10 23:53:39
BalloonType REG_DWORD 0x8
ActionCenterNotificationCount REG_DWORD 0x4
ActionCenterLastPossibleRestartNotification REG_SZ 2018-10-04 10:00:00
LastRestoreId REG_SZ {3359D5B5-BE91-413C-9203-D517DE682170}


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Detect
LastSuccessTime REG_SZ 2019-01-10 23:34:15
LastError REG_DWORD 0x0


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Download
LastSuccessTime REG_SZ 2019-01-10 23:59:48
LastError REG_DWORD 0x0


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Results\Install
LastSuccessTime REG_SZ 2019-01-10 23:38:08
LastError REG_DWORD 0x80070643


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\UAS
UpdateCount REG_DWORD 0x1


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting
BatchFlushAge REG_DWORD 0x1fc
SamplingValue2 REG_DWORD 0x30a


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\RebootWatch


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending
ValidatedPreWsus3RegistrationRequests REG_DWORD 0x1


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup
SelfUpdateStatus REG_DWORD 0x0
SelfupdateUnmanaged REG_DWORD 0x0
 
Post the logfile C:\Windows\WindowsUpdate.log as attachment in your next reply.
Note: if the file is too big to upload to your next reply please upload via a service such as Filedropper or One Drive or SendSpace and just provide the download link.
 
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