📎 AI Summary:
The thread discusses issues encountered after updating to Windows 10 build 10049, where the original poster experiences continuous reboots without success in booting into safe mode, despite troubleshooting efforts. The respondent suggests the possibility of automatic recovery after multiple failed boot attempts and recommends creating a bootable USB with an earlier build (such as 10041) to access recovery options. Overall, the exchange centers on troubleshooting boot problems following a Windows 10 update, with suggestions aimed at restoring system access.

Safal Piya

Active Member
Joined
Jun 16, 2014
Messages
26
Thread Author #1
I had recently updated my computer to the windows 10 build 10049, everything was going fine but tonight I found a problem in my computer. The computer reboots automatically after the booting screen (Check my uploaded picture) and the reboots continues. I cannot boot into the safe mode too. I had tried to unplug my computer, checked my ram, cleaned everything, But this problem isn't solved. If the windows 8 disk can solve this problem please reply and help me.
 

Attachments

  • WIN_20150416_103354.webp
    WIN_20150416_103354.webp
    15.5 KB · Views: 347
Solution
Sometimes after the third boot attempt the system will automatically go into the Recovery options. I suppose you are not seeing this?

You could download one of the .iso file for perhaps 10041 and set up a USB flash drive as install media. You could then boot to it and have access to Recovery options.

You may have gotten some type of driver update and it could be causing the problem.

Saltgrass

Excellent Member
Microsoft Community Contributor
Joined
Oct 16, 2009
Messages
15,153
Sometimes after the third boot attempt the system will automatically go into the Recovery options. I suppose you are not seeing this?

You could download one of the .iso file for perhaps 10041 and set up a USB flash drive as install media. You could then boot to it and have access to Recovery options.

You may have gotten some type of driver update and it could be causing the problem.
 

Solution