This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My PC boots up normally as it should when just, booting it up.
However, if I choose the restart option in my Windows it does not restart.
It shuts down, boots up and 'freezes' on the ROG screen where I should be able to press F2 or DEL to enter BIOS.
The F2 and DEL key is not opening BIOS when I restart my pc, it does when I boot it manually.
I have this issue for a while now, but I straight up ignored it as it wasn't a problem for me, but now I want to update my Windows and I can't.
The update installation fails because, well, the system does not reboot when it needs to be rebooted. Blocking me to do any updates that require a reboot.
I don't know if this matters, but here's my specifications:
CPU: Intel i7 7700k
GPU: NVIDIA GeForce GTX 1070TI Founder Edition
MB: Asus ROG Strix Z270f
Drivers:
Fastro MS100 1TB
Samsung SSD 860 EVO 250GB
SanDisk SDSSDHII240G
What I've tried so far:
Disable second and third boot option. (This however doesn't save, the boot order does, but disabling a second or third boot option does not? After a bit of Googling this is known issue with Asus motherboards)
Repairing drives using chkdsk/f C: in a command prompt.
Restored and repaired system files using DISM.exe /Online /Cleanup-image /Restorehealth in a command prompt.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
As the reboot freezes on the Rog screen, it is more likely that it is a hardware problem, you can try to disconnect the hard drives and try boot using only the primary drive, to check if is not having an incompatibility issue between the drives or if one of them is slowing down the reboot.
If one of the drivers is empty or doesn't have important files, you can try to perform a clean installation of Windows on the drive to check if the reboot problem will happen in the installation process.
Hi, NietRobijn,
Sorry to hear you're experiencing this issue.
A common cause for this problem is an outdated Bios version, check if you are running the latest version of the Bios. You can check which Bios version you are using on the System Information page.
1-Right-click on Start then click on Run
2-Type: msinfo32 and click on OK
3-Search for the Bios Version/Date
4-If you are using a version earlier than 1501, you can download the latest Bios version at this link.
https://www.asus.com/supportonly/strix%20z270f%...
Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
Another possible culprit for this error is the Fast Startup setting, disabling it might fix the problem.
1-Right-click on Start then click on Run
2-Type: Control Panel and click on Ok
3-Click on System and Security
4-Click on "Change what the power buttons do" under the power option
5-Click on "Change settings that are currently unavailable", then uncheck the option "Turn on fast startup"
6-Click on Save changes and reboot your pc
That was it! My M.2 drive did some wierd stuff that prevented the PC from rebooting, I've got no clue, but: it works. So whatever it did, it works. Haha!
Never had Fast Startup enabled, so that's definitely not it.
My BIOS version was indeed outdated, running on 1203.
Updated it to 1501, but it didn't effect it either, I checked the BIOS and it is now indeed on 1501.
Shortly said; problem still exists after these changes.
