Can't restart. Re-start circle(?) just goes round and round endlessly

pepanee said:

Have you tried clicking the link in the bottom right picture?
"Search for updated drivers on Windows Update"

No. I haven't tried clicking the link. But I just did (see below):

Attachment 390259

The more I think of it, the more I suspect that this error might be trace-able to this error which first showed up last March 30. I never had this problem prior to March 30. Lots and lots of users are experiencing this problem for the first time also:

New MSFS error in graphics - Microsoft Flight Simulator (2020) - The AVSIM Community

Attachment 390260

These users think the error is either caused by Microsoft's Flight Simulator Program whereas Microsoft believe it's an nVidia issue. It could be a combination of both.

Yea, could be possible that it's that other issue you just mentioned. But in that Windows Update window, press
View optional updates
and see if you can find drivers you can update there.


Also, if you want to try my optional idea of "disabling" this unknown device, and trying to Restart / Shut Down.

The thing is that if anything happens, which I don't think would, then you would want to know how to go to Safe Mode, and re-enable that device.

It's probably ok to disable... I created a restore point about half an hour ago. I also have a disk image.

Any idea if disabling a device might affect hardware and permanently damage it (ie. PC won't work even after restoring an image)? Windows disabling a CPU. Is that even possible? The only experience I have of software affecting hardware was a long time ago. I was playing around with monitor resolutions. I played with the wrong settings which literally burned the monitor (I could smell and see smoke coming out at the back of the monitor, called 'CRT' in the old days).

hah, yea the old days technology had issues.
There won't be any hardware damage if you disable it. Just worst case scenario that the computer wouldn't want to start up, which I highly doubt would happen. If that happens, turn off the computer, try to turn it on, and if it won't start, turn off again. And then turn on. After a few times, it will give you the option to start the computer in Safe Mode. With Safe Mode, you can go right back to Device Manager and re-enable it.

The thing is that let's hope that we have pin pointed it down to this. I'm hoping that this driver issue is causing your Windows to lag by Shutting Down / Restarting, because it's trying to identify that driver or something...
...and if we disable it, and Windows is okay with that, then let's hope we go for the win!


Edit: I wouldn't worry about any physical hardware damage at all. Because we are not overclocking anything, we are not modifying anything that changes how the hardware works. All we are doing is making Microsoft Windows ignore that device driver; it's all software related.

pepanee said:

hah, yea the old days technology had issues.
There won't be any hardware damage if you disable it. Just worst case scenario that the computer wouldn't want to start up, which I highly doubt would happen. If that happens, turn off the computer, try to turn it on, and if it won't start, turn off again. And then turn on. After a few times, it will give you the option to start the computer in Safe Mode. With Safe Mode, you can go right back to Device Manager and re-enable it.

The thing is that let's hope that we have pin pointed it down to this. I'm hoping that this driver issue is causing your Windows to lag by Shutting Down / Restarting, because it's trying to identify that driver or something...
...and if we disable it, and Windows is okay with that, then let's hope we go for the win!

Another possible clue first. The screen below popped up when re-start failed after the repair-install (basically new Windows installation). At this point in time I didn't have sound and network connectivity (missing drivers and no way to install them since I don't have an optical drive).

I'm speculating that the reason re-start and shutdown have very long run times is that "ScreenShot Uploader" (see below) is delaying the re-start and shutdown. The ScreenShot Uploader's icon is a Steam icon. What's interesting about that icon is that I only have one Steam game installed in the PC, and that one game is Microsoft Flight Simulator. Perhaps ScreenShot Uploader or the Steam client is calling "home" and unsuccessfully at that. A google of ScreenShot Uploader however didn't help.



Edit (Addendum): I did a test earlier and booted in Safe Mode a couple of times. In Safe Mode (which doesn't load drivers), Re-start and Shutdown work normally ie. PC re-starts or shutdown quickly (within 10-15 seconds).

You know what. You have a good point. I completely forgot about this picture you uploaded earlier. Let's try it this way first!
THIS is probably it. So sorry I forgot about this.

Turn on your computer normally.
Go to Task Manager -> Processes tab

Look for that Steam icon app / text of "Screenshot Uploader"

End its task. Look through the whole list, make sure there's no other Steam icons or whatnot running.

After that, try the Restart.

Yes. I think you're right. This looks like it's most definitely the issue.

Screenshot Uploader disabled, but still runs and prevents shutdown :: Help and Tips
Screenshot uploader - shut it off - Don't want it, don't need it :: Suggestions / Ideas

Multiple posts on the internet saying they have the same issue Shutting Down / Restarting the computer.


You're going to have to Disable this in Steam. Yet these posts say they have disabled it, and still causes issues.


OPTION TWO:
We can make Windows automatically end ANY task that it is lagging on.
Let me look online for the source on how you can do that real quick.

Another dead-end.

I disabled Base System Device. No difference. Problems still exist.

I took a look at Task Manager. Nothing there either.



---

Okay re-enable Base System Device. It is not the issue.

In Task Manager -> Details tab, can you find anything Steam, Screenshot Uploader exe?

See below. I checked this previously. Nothing's changed since I last checked it yesterday. Problem remains.



Also, I have never used Steam's screen cap.