Solved Windows 10 Reboots
-
What hardware is it?
-
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Obsolesce said in Windows 10 Reboots:
A/V / driver issue?
I decided to check the windows updates - I saw on another page that Was there problem.
here is what I see.Try to install it and see if it Reboots
during install It says it's pending Download,. fails, and now is downloading.
-
@wrx7m said in Windows 10 Reboots:
What hardware is it?
I think this is one of our Nobilis PC's . Off top of my head im not exactly sure.
-
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
-
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Does it still happen while in safe mode?
-
@black3dynamite said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Does it still happen while in safe mode?
Im remote only right now.
This site is like 3 hours away from me, so I have no way of testing that. -
https://i.imgur.com/mwLQC7V.png
This is what I see now in the system Events viewer.
https://i.imgur.com/Lc5TCQa.png
*edit *
-
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
-
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
Not my choice on buying a new Pc or downgrading.
-
@WrCombs said in Windows 10 Reboots:
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
Not my choice on buying a new Pc or downgrading.
So I take it there are no Win10 drivers installed then?
-
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Obsolesce said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
Ran updates and restarted the PC, since then it's rebooted twice..
same issue..
Update all drivers from the PC manufacturer to their latest Win10 drivers. If they don't have Win10 drivers, downgrade to 8.1 or 7, or but a new PC.
Not my choice on buying a new Pc or downgrading.
So I take it there are no Win10 drivers installed then?
Not that I'm seeing, all it says is the "best driver" is already installed.
-
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
-
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot. -
@WrCombs said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot.The Fixit? none that I know of.
-
@Dashrender said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot.The Fixit? none that I know of.
I'll give it a shot and see if that fixes it then .
-
DISM and sfc /scannow are your friends. Just make sure that you launch the cmd window as administrator
-
@scotth said in Windows 10 Reboots:
DISM and sfc /scannow are your friends. Just make sure that you launch the cmd window as administrator
-
@Dashrender said in Windows 10 Reboots:
@WrCombs said in Windows 10 Reboots:
@Dashrender said in Windows 10 Reboots:
That seems a bit of the top for a suggestion - not saying it's wrong, but I've never seen the requirement to get a new machine because Windows 10 was installed and something was causing it to reboot.
Personally - I'd wipe and reload it long before buying a new machine, but you're remote, so that's a harder decision.
Have you used the MS Fixit tool for Windows Update? that might do the trick.
what damage could it do?
I'll give it a shot.The Fixit? none that I know of.
did not find anything either.
-
@WrCombs said in Windows 10 Reboots:
@scotth said in Windows 10 Reboots:
DISM and sfc /scannow are your friends. Just make sure that you launch the cmd window as administrator
This is good. In addition to sfc, DISM will restore your local store of Windows files to put back in place in case of corruption / issues with the installation. One other thing to try is a chkdsk /f or /r if you want. These are just insurance moves if the logs don't reveal anything obvious.
-
Also from an administrative cmd prompt, you could run start /w cleanmgr.exe and get rid of stale update files, old installations, ... I usually keep dump and log files. It takes a while for a restart if you remove any update files because it rebuilds your updates database during restart.
