EMERGENCY - Boot Loop After Win Update

See if you can make progress with Ubuntu / Linux.

zbook said:

See if you can make progress with Ubuntu / Linux.

But was c: the correct drive? Should I use the e: drive?

No offense but when I ask questions you don't seem to answer them directly or you miss them entirely.

I would suggest you just use the boot-repair tool included in Macrium Reflect Free v5: How to fix Windows boot problems (Restore, Windows PE) Fix Boot Problems It works the same in all versions of MR

After all the above I suggest your restore back to 1709 and start over

Go Back to the Previous Version of Windows in Windows 10 | Windows 10 Tutorials

The drive letter used by Windows is very often different in Windows PE.
The disk numbers and volumes may be different in a normal boot and in Windows PE.
The computer in this thread was always examined in Windows PE and in Windows PE it was E:
However with a normal boot it may very well be C:

zbook said:

The computer in this thread was always examined in Windows PE and in Windows PE it was E:
However with a normal boot it may very well be C:

So in my case the drive letter is E within win PE according to your observation. In that case I'll just change that in the command and try again.

I tried the option to go back to the previous build in the Advanced Startup options in win PE. But after I opted for it, it said it can't go back to the previous build. If that's the case would your command be useless anyway?

Hi zbook,

I entered your command. Take a look at the image. It basically says the package isn't a valid windows package.. error: 0x800f0805.

It also said that the scratch directory size might be insufficient to perform the operation... and to use the /scratchdir option to point to a folder with sufficient scratch space.

What do you make of this?

Steps and images are missing.
It is unclear what is happening on the computer.
Were you using a Windows 10 iso build 1511 to repair a Windows 10 iso 1803 ?
The first image that was displayed in post #3 indicated: Windows version 10.017134.1
The last image that was displayed in post #36 indicated: Windows version 10.0.10586
How did you go back in time from version 10.0.17134.1 to 10.010586?
This was 1803 to 1511.
The steps I can no longer follow.
The options for troubleshooting/fix now appear to be: Ubuntu or Macrium or clean install.

Hey zbook,

Great news! I was able to get to my desktop through safe mode. After using the macrium tools for repair as you suggested I was met with a screen that said my PC was being updated and repaired.

Now I'm backing up my files to my flash drive in safe mode before I attempt to do a regular boot.

The only issue is that I got to reinstall all my programs like Word, Excel, etc since these don't work after the PC recovered.

Appreciate all your help my man! Let me know if there's something I need to do just in case this thing goes bad again.

You are welcome.
There were steps posted by Clintlgm.
If you followed those steps then please let Clintlgm know.

Consider the repair fragile.
1) Create a brand new restore point
2) Once you have a stable computer environment > make a new Macrium backup image
3) Open disk management > widen each of these columns: Status and Volume > make sure that each column has been sufficiently widened so that none of the text is cut off and all characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of | Windows 10 Tutorials
4) Run the BETA log collector and post a zip into this thread:
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)
Use the text and images in this thread in case there are any problems running the beta log collector: (post #5)
DM Log tool problem Solved - Windows 10 Forums
5) open administrative command prompt and copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /restorehealth
8) chkdsk /scan
9) 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

zbook said:

You are welcome.
There were steps posted by Clintlgm.
If you followed those steps then please let Clintlgm know.

Consider the repair fragile.
1) Create a brand new restore point
2) Once you have a stable computer environment > make a new Macrium backup image
3) Open disk management > widen each of these columns: Status and Volume > make sure that each column has been sufficiently widened so that none of the text is cut off and all characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of | Windows 10 Tutorials
4) Run the BETA log collector and post a zip into this thread:
https://www.tenforums.com/attachment...-v2-beta10.zip
(extract > open)
Use the text and images in this thread in case there are any problems running the beta log collector: (post #5)
DM Log tool problem Solved - Windows 10 Forums
5) open administrative command prompt and copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /restorehealth
8) chkdsk /scan
9) 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

Hi zbook,

Appreciate the help. I did all that you asked. But one strange thing happened when I put in of your commands in the command prompt. As the command was in the process of doing its thing, I right clicked on the properties of the command prompt window to tinker with the background color and text size of the prompt. As I did this a message popped up saying that my PC needs repair and needs to restart.

I restarted and sadly the PC went into boot loop again - the nightmare again. I dont know if my tinkering with the command prompt properties triggered this reaction. But luckily I went into safe mode and then booted into regular boot and now everything is ok now. What happened is something I cannot explain. Again luckily I am now able to boot into my PC. After that I went ahead and redone all that you asked. Below is the info that you requested:





---ATTACHMENT - BETA LOG COLLECTOR---
DESKTOP-CS2L7VM (2018-05-21 00 48).zip




---RESULTS FROM COMMAND PROMPT---

Microsoft Windows [Version 10.0.17134.48]
(c) 2018 Microsoft Corporation. All rights reserved.

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 found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

The system file repair changes will take effect after the next reboot.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.48

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
504576 file records processed.
File verification completed.
4333 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
1463 reparse records processed.
595128 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
1463 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
45277 data files processed.
CHKDSK is verifying Usn Journal...
41102160 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

467865018 KB total disk space.
268142316 KB in 275822 files.
179092 KB in 45278 indexes.
0 KB in bad sectors.
628486 KB in use by the system.
65536 KB occupied by the log file.
198915124 KB available on disk.

4096 bytes in each allocation unit.
116966254 total allocation units on disk.
49728781 allocation units available on disk.

C:\WINDOWS\system32>