Windows 10: Repeated Crashes and Boot Errors Apparently Caused by Driver Updates

Happy Easter.

Any further instructions on diagnostics? I'm in something of an awkward situation with this borrowed laptop, given how long I've had it, and if possible I really need to determine this week whether my machine can be returned to its proper condition or whether I need to replace it.

EDIT: If fixing it seems a distant possibility, I'm at least going to need to completely block updates so I can use internet again.

 

Where did everybody go? : (

 

When you power on what do you see?
What are the current problems?

 

Power-on is normal, and everything seems to be working fine. But as soon as I reconnect to the internet, the Windows 10 update assistant starts downloading that same update that my system found indigestible. As I still don't know the root cause of the update failures and failed boot, surely I'll find myself back in the same situation if I try to resume normal activity?

 

Have you made backup images with Macrium?
Is/are there valid restore points?

The problem now is unexpected update attempts?
Or update failures?

Run the beta log collector and post a new zip into the thread:
log collector v2-beta08.zip
(extract > open)

 

When I run the log collector and hit ENTER, I get a couple seconds of text and then the window disappears. Is there something else I'm supposed to be doing?

Thanks.

 

See post # 5 in this link:
DM Log tool problem Solved - Windows 10 Forums

 

Please see the questions in post #95.
The log collector did not produce any files.

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) run the BETA log collector with a different browser after the above commands.

 

I have not backed up with Macrium. I have three system restore points listed, two automatic.

The problem is that (a) Windows updates were routinely failing for a reason that earlier in this thread we did not determine, and (b) the forced restarts triggered by these updates eventually messed up the boot, hence the situation I was in a few weeks ago and, with your help, dug myself out of. But unless I missed something, we have not found the root cause, and so it's likely to happen again as soon as I let the updater do its thing. At absolute minimum, if no other solution seems possible, I want to be able to halt updates completely so I can squeeze a few more months' use out of my machine. Right now, I'm stuck using my laptop without internet to prevent the update from downloading automatically.

I am running those commands now. Recall that I did run them several weeks ago at your behest, with the results published in post #80.

 

Within 30 days the Windows operating system will change. Today is 4/4 and sometime after 4/10 (probably before the end of the month) there will be a major Windows upgrade to 1803. The upgrade should change the registry and operating system. So the best option may be to wait or the major upgrade?

What happened with the administrative command prompt command results, and beta log collector using a different browser?

 

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\windows\system32>sfc /scannowBeginning 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.C:\windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\windows\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is OS.Stage 1: Examining basic file system structure ... 641024 file records processed.File verification completed. 38725 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 730966 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 44972 data files processed.CHKDSK is verifying Usn Journal... 34203576 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 975633897 KB total disk space. 628810276 KB in 348724 files. 202336 KB in 44973 indexes. 0 KB in bad sectors. 795921 KB in use by the system. 65536 KB occupied by the log file. 345825364 KB available on disk. 4096 bytes in each allocation unit. 243908474 total allocation units on disk. 86456341 allocation units available on disk.C:\windows\system32>

 

I'm not sure what you mean by "a different browser" for the beta log collector. It's a PowerShell shortcut, right?