No Screensaver after 10 update

robinski78 said:

Any suggestions welcome...

So you've tried all the suggestions contained within this thread?

wittzi said:

So you've tried all the suggestions contained within this thread?

By and large, yes, where applicable to my equipment... I've tried everything I can think of, or that which seems logical...

It would appear that so many different approaches have been made, by members trying to outfox the bug... I would sooner wait for Microsoft to come up with a stable answer that will fix the problem once and for all...
That's if they can...

Reading in other locations, it seems as though a SS is not a necessity any more... To be sure though, I find it best (at the moment) to put the equipment to sleep for short or longer breaks...

Will still keep my eye on this thread, for any positive suggestions...

Thanks for your interest...

Robbie...

adsrox0r said:

The registry edits appear to have resolved my problem for now. I'll be treating it as a temporary bodge until Microsoft hopefully sort this annoying little mess out.

I think this problem is more complex than it appears, A number of users appear to have resolved the problem using suggested registry edit, but not all.
I have looked at my Registry ProfileList and have 4 S-1-5-21 (longstring) entries which are correct so the problem would appear to be somewhere else for me !

robinski78 said:

By and large, yes, where applicable to my equipment... I've tried everything I can think of, or that which seems logical...

It would appear that so many different approaches have been made, by members trying to outfox the bug... I would sooner wait for Microsoft to come up with a stable answer that will fix the problem once and for all...
That's if they can...

Reading in other locations, it seems as though a SS is not a necessity any more... To be sure though, I find it best (at the moment) to put the equipment to sleep for short or longer breaks...

Will still keep my eye on this thread, for any positive suggestions...

Thanks for your interest...

Robbie...

I am also following the same approach, without a rational explanation as to why this is happening it is too risky to blindly follow. It's not necessary on modern displays, but it should still work if available.

Heres my scenario...

Cold boot...after startup screensaver will not activate, check screensaver settings, it has defaulted to one minute timeout.
If I change it to 2 minutes click apply and then change it back to 1 minute and click OK, after one minute it will activate.

Thats the only thing I change, so it seems somewhere on the initial start, that the screensavers failing.

Also if you set it for 5 mins and OK it, when it cold starts again its back to one minute, to me the bug is there
somewhere ???

Such a simple thing, such frustration !

Andy

amason said:

Heres my scenario...
Cold boot...after startup screensaver will not activate, check screensaver settings, it has defaulted to one minute timeout.
If I change it to 2 minutes click apply and then change it back to 1 minute and click OK, after one minute it will activate.

Thats the only thing I change, so it seems somewhere on the initial start, that the screensavers failing.

Also if you set it for 5 mins and OK it, when it cold starts again its back to one minute, to me the bug is there
somewhere ???

Andy

I think this is the problem for many of us where the console lock fix isn't working. The initial startup of the screensaver is failing.

I have tried everything I can think f, even compared screen for screen the setting of one computer that works to the other computer where it doesn't work and can't find anything.

So there is another thread on this issue and it has people unplugging their joysticks from their computers to fix the issue. Well I tried it and HOLY MOLY it fixed my issue as well. I plugged it back in and ran the Windows test on it and I can't see any movement from it so I don't see why it is allowing it to work. I guess for now I'll just have to plug it in when I play games and unplug it when I'm done. The other thread is located here if anyone wants to look through it. Linky

hattrik21 said:

So there is another thread on this issue and it has people unplugging their joysticks from their computers to fix the issue. Well I tried it and HOLY MOLY it fixed my issue as well. I plugged it back in and ran the Windows test on it and I can't see any movement from it so I don't see why it is allowing it to work. I guess for now I'll just have to plug it in when I play games and unplug it when I'm done. The other thread is located here if anyone wants to look through it. Linky

I saw that too. I am glad you found out what your problem was and the fix for it. I also read about wireless mouse causing issues. In my case, I don't have any joysticks or wireless devices so that isn't my problem.

Emb, just for curious sake if you launch a command prompt with admin privileges and type in powercfg -requests, does it list anything? Make sure all other programs are closed.