No Screensaver after 10 update

Hmm no joysticks or game controllers on my PC and still no Screensaver. Maybe I will unplug all my peripherals from the USB ports and see what happens.

Ok so I went into my device manager and disabled all my USB devices and then restarted my PC. Screensaver is working like it should now. I then went back and start to enable one device at a time to see if I can find the problem device but I end up enabling every device and the Screensaver is still working. I have no idea what fixed it but I really don't care, as long as it works.

Raydee said:

Ok so I went into my device manager and disabled all my USB devices and then restarted my PC. Screensaver is working like it should now. I then went back and start to enable one device at a time to see if I can find the problem device but I end up enabling every device and the Screensaver is still working. I have no idea what fixed it but I really don't care, as long as it works.

That's a bit like sod's law taking a hand... Must have been awfully frustrating... A real head-banger...

Emb said:

If I set the screensaver to a given time (lets say 10 minutes) and then I do a "restart" the time of 10 minutes is still there and works fine. But if I set the time (10 minutes) and do a "shut down" and the start the PC the screensaver is defaulted to 1 minute again and doesn't work. Yes, I too received the update. I hope you have better luck then I.

I have the same problem. Is there a true fix? I remember this happened to me in XP, but I can't remember what I did to fix it.

Raydee said:

Ok so I went into my device manager and disabled all my USB devices and then restarted my PC. Screensaver is working like it should now. I then went back and start to enable one device at a time to see if I can find the problem device but I end up enabling every device and the Screensaver is still working. I have no idea what fixed it but I really don't care, as long as it works.

Actually, that sort of makes sense. Windows has, for quite some time, come with important registry settings that we don't have direct access to control (even the key name is cryptic), but turning off features and turning them back on could be resetting a corrupt setting. I've had Windows completely corrupt the SYSTEM registry hive, which prevents Windows from being able to boot, even in Safe Mode. You can imagine the fun I had in repairing that (a repair install of the OS didn't do it) because I wasn't about to wipe a start over (I was 1000+ miles away from home at the time).

I still miss the days of a the INI files (aka text file for the settings). Even unix systems still use text configuration/settings files for most (99%, I think) programs. The registry has always been my biggest complaint with the post WfW 3.11 releases (I seem to recall that even Win95 started to shift away from the INI files).

Ok so I think I found the culprit, it looks like my Logitech G35 headphones may be the problem. As soon as I enabled them in the device manager the screen saver stopped working again. I have them plugged into a USB hub so I am going to try to connect them directly to the pc and see what happens.

Raydee said:

Ok so I think I found the culprit, it looks like my Logitech G35 headphones may be the problem. As soon as I enabled them in the device manager the screen saver stopped working again. I have them plugged into a USB hub so I am going to try to connect them directly to the pc and see what happens.

I assume the mic doesn't have an "on/off" switch. If it does, try turning it off. I do have a webcam (with mic) attached without an issue, though. I was afraid it might pic up the noise in this computer room (several systems running makes a lot of fan noise), but that isn't preventing the screen saver or power management. Surely, Microsoft wasn't so stupid as to only exclude webcam mics from the activity test. That would really be showing ignorance in both the testing AND development of Windows 10.

The "release" Windows 10 certainly does have the "open beta" feel to it. Then again, that could pretty much be said about every version of Windows throughout history. Before they actually get one version completely fixed, they stop working on it and force everyone to accept it as-is or upgrade (to fix some things and break others). I recall the exact reason why (and when) I switched off of Windows 98. I got myself a new CD burner (may have been a DVD burner, actually) that Windows 98 wasn't detecting properly. No drivers were able to "fix" the issue, so I foolishly "upgraded" to Windows ME (there was no Might Explode about that, either). It fixed the burner issue, but totally messed up with so many other things. In less than a month, I went from Windows 98, to Windows ME, followed closely by Windows 2000. All of that was due to a simple driver issue with Windows 98. I lost my true DOS mode (for legacy gaming) on that system, all in the name of bringing discs. Now, here we are, jumping through hoops to get the most basic of options (screen savers and power management) to work under Windows 10 (or it is really 6.3?! of course, Windows ME was 4.90, so what's really in a version number).

Same here. Upgraded from 8.1 to 10 and no sleep, no screensaver. Everything else works tickedy-boo. I have an HP all-in-one, no separate monitor. Everything is indentified correctly. Everything updated. All settings available, but changing them does nothing.

I have heard this can be a .NET issue for some folks.

I have also tried the BURIED setting for allowing the computer to sleep even if sharing media.

No joy.

Anyone know anything fancy?

Raydee said:

Ok so I went into my device manager and disabled all my USB devices and then restarted my PC. Screensaver is working like it should now. I then went back and start to enable one device at a time to see if I can find the problem device but I end up enabling every device and the Screensaver is still working. I have no idea what fixed it but I really don't care, as long as it works.

Makes me wonder if my USB wireless adapter is the culprit...

Disable fast start up in power options. It is default in windows 8 and 10. Windows 7 did not have this. Fixed it for me. Stopped PCI recourse allocation errors too.