Windows 10: "Windows PC did not start correctly" on loop

I recently installed the latest Windows 10 update and noticed my computer was slower afterwards (computer game would start lagging and alt+tab would take longer to actually switch between game and other apps). I disabled nearly every background app and some startup apps but that didn't fix anything. I then tried a system restore to before the update, but after my computer booted again, it said there was an error. I then tried to revert back to the last Windows version and that's when I started getting the "Windows PC did not start correctly" loop.

The system repair option fails. The system restore option failed and now there isn't a restore date available. The computer reset option failed. Booting into safe mode fails. No matter what I do I can't even get to the log-in screen.

I have tried various command prompt entries including scannow and still nothing.

Any suggestions are appreciated! Or even suggestions as to where I could get help (I just got this PC in July the manufacturer has a 1-year hardware warranty).

:)

 

Enter on keypad " no. + # "

petrib is correct. It is a shortcut to SIM numbers.

Numbers on your SIM might not be in the position you think. Just because they appear sorted in alphabetical order in the contacts list doesn't mean that they appear in that same order on the SIM. On the SIM they appear in the order in which you input them,
unless you delete a number in which case the next one entered takes its place.

 

Enter on keypad " no. + # "

Hello guys :smileyhappy:

There's something make me crazy :s
When I click a certain number on keypad on any NOKIA mobile
Then click the symbol " # ", then a number of
a contact "in my contact list" will be appeared.
Is there anyone know how is that???
I feel curious toward this puzzle :smileyvery-happy:
OK., if anyone know about this topic, please tell me :smileysad:
Anyway thanks :smileywink:

 

You can try below Windows repair instructions one at time and each time you have completed a instruction reboot your computer to find out boot issue resolved if not try next repair instruction.



Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below commands into Command Prompt and press Enter key.

Following commands will repair Master Boot Record (MBR), Boot Sector and BCD Store.


Code: Bootrec /FixMbr Bootrec /FixBoot Bootrec /RebuildBcd[/quote]






Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Code: Sfc /Scannow /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows[/quote]

Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.







Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

Following command will fixes errors on the disk and locates bad sectors and recovers readable information.


Code: Chkdsk D: /r[/quote]
Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.








Windows Vista/ 7/8/8.1/10 keep a regular backup of the registry handy in case you need to overwrite a corrupted registry. By default, the RegIdleBackup task runs every 10 days, so that’s as far back as you would lose if you replaced the current registry with the automatically backed-up files. You can find the backed-up registry files in \Windows\System32\config\RegBack folder.





Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

Code: Dir C:\Windows\System32\config\RegBack[/quote]
Above command will list files stored within RegBack folder and there file size, make sure files are not zero size if they are do not follow below instructions.





Please replace partition letter C: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

Please type below commands into Command Prompt and for each command you have typed press Enter key.



Code: Ren C:\windows\system32\config\SAM SAM.BAK Ren C:\windows\system32\config\SYSTEM SYSTEM.BAK Ren C:\windows\system32\config\SECURITY SECURITY.BAK Ren C:\windows\system32\config\DEFAULT DEFAULT.BAK Ren C:\windows\system32\config\SOFTWARE SOFTWARE.BAK Copy C:\Windows\System32\config\RegBack\SAM C:\windows\system32\config Copy C:\Windows\System32\config\RegBack\SYSTEM C:\windows\system32\config Copy C:\Windows\System32\config\RegBack\SECURITY C:\windows\system32\config Copy C:\Windows\System32\config\RegBack\DEFAULT C:\windows\system32\config Copy C:\Windows\System32\config\RegBack\SOFTWARE C:\windows\system32\config[/quote]
This procedure assumes that Windows Vista/7/8/8.1/10 is installed to the C:\ partition. Make sure to replace C:\ drive letter to the appropriate Windows OS installed partition drive letter if it is a different location.


Above commands renames the registry files at their existing location, and then copies the registry files from the RegBack folder to the C:\Windows\System32\Config folder.

 

Look for performing an in place upgrade on here if non of that works.

 

To perform a in-place upgrade Windows 10 setup need to be run from booted working Windows 10 OS.

 

Ah, forgot that.

 

If you don't have Windows 10 installer media, you can download the Windows 10 ISO image and burn the image to DVD or USB Flash Drive with the Media Creation Tool.
Once you have a Windows 10 installer DVD or USB Flash drive, you can boot from that and choose your language, then Repair Your Computer.
If this fails, it will take you to the RE (Recovery Environment) Here, you can choose Command Prompt.

At command prompt (x: sources) type this exactly as written:
bcdedit |find “osdevice” (Must inc ” and the |), the | before Find is the Upper case \ key) press enter. This will tell you what drive letter the OS is on. It may not be on the C: drive.
Now use the returned as the drive letter for OS, for this example, assume C: or whatever drive letter is the os device.
At the x sources type: chkdsk c: /r press enter, 5 stages of check disk will run. It will test the HDD for errors. it may take a while.
Or you can run the previously discussed commands.

 

Unfortunately none of these things worked. When I tried to run CheckDisk I got a "failed to transfer logged messages with status 50" error message.

I also at some point got a "c/windows/system32/logfiles/srt/srttrail.txt" message, I think after trying a reset again.

Any further suggestions would be great. I'm probably going to start by calling Microsoft support because I'm 95% sure this all started when I installed their most recent update.

Is it possible that disabling something in the startup tab of task manager is responsible for this? I can't imagine they would put some vital program in that tab, making it so easy to disable.

 

No those are startup programs not needed to boot Windows OS.

"Failed to transfer logged messages to the event log with status 50" error message usually occurs due to two main reasons: there are corruptions or bad sectors in Windows partition or you run Check Disk utility from an installation disk which you did.


If you have a USB Flash Drive connected to you computer and copy srttrail.txt file to USB Flash Drive and post the srttrail.txt for us to view the file.

You can execute below command to copy srttrail.txt file to USB Flash Drive.

Code: Copy c:/windows/system32/logfiles/srt/srttrail.txt X:[/quote]
Replace X: with drive letter assign to USB Flash Drive.

You can find out which drive letter assign to USB Flash drive by executing below commands.


Code: Diskpart list volume[/quote] Type Exit command to exit Diskpart.

 

Ok I will try that when I get home from work.

 

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎1/‎4/‎2018 7:24:20 PM (GMT)
Number of repair attempts: 24

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 109 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 562 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 3360 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 188 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 1516 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 343 ms

Test Performed:
---------------------------
Name: Access control test
Result: Completed successfully. Error code = 0x0
Time taken = 5907 ms

Test Performed:
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 132109 ms

Test Performed:
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
A patch is preventing the system from starting.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
Time taken = 1163172 ms

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 1250 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 313 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Root cause found:
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 563 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 328 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 63 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 46 ms

Root cause found:
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.

---------------------------
---------------------------

 

Please execute below command and reboot your computer to see issue resolves.


Code: DISM /Image:C:\ /Cleanup-Image /RevertPendingActions[/quote] Replace C:\ drive letter with Windows 10 installed partition drive letter.

Restart your computer to find out issue resolved.

 

Thanks for all the responses.

What ultimately fixed it was going into the troubleshooting menu and selected "start from cd, dvd, usb" and then instead of choosing the "start from dvd or cd" option I tried the "start from UEFI DVDRam" option. When it restarted it pulled up a similar screen to when I chose the "start from dvd or cd" option in the past where it gave me the option to install Windows. But this time I clicked the Install option and a partition was actually available to install Windows onto. It ran through some steps and restarted my compute and it worked.

All my programs were deleted but I didn't really have many so that wasn't an issue. Didn't actually check if my files were still there but I'm going to assume they are gone as well (again, didn't really have anything important).

 

We are glad to hear your issue has been resolved, thank you for letting us know that all is now well!