Photos Screensaver ignoring power settings that Turn off the displ

I've found an issue with the Vista Photos screensaver. I have set as default
to use images in the \pictures folder. I have roughly 400 images in two
separate directories in the \pictures folder. The photos screensaver
displays all the images just fine but, it won't allow my display to turn off
at time specified in power settings.

I have the screensaver set to turn on at 5 minutes of inactivity. If I have
the Vista power settings set to "Turn off the display" after say 10 minutes
or longer, it is ignored. The monitor continues to stay on and display the
screensaver and never turns off. I tested with the different Photos themes,
shuffle on and off and different speeds for that screensaver and same issue.

I found a couple of forum threads on other sites from a few months ago that
show some other people describing same issue. It appeared it had something to
do with having more than 50 images in the \pictures folders. So, what I did
was test that and I could duplicate that scenario. I think it really does
have to do with the amount of images in the \pictures folder and subfolders:

51 images or more - Display will never turn off at specified amount of time
50 images or less - Display will turn off at specified amount of time

Any of the other Vista screensavers do not prevent the display from turning
off. It's only the Photos screensaver.

I can duplicate this problem on TWO separate systems:

A Desktop (home built) running Windows Vista Ultimate 32-bit SP1
A brand new Laptop (Dell M1530) running Windows Vista Home Premium 32-bit SP1
Both computers have latest bios and drivers. The laptop is brand new.

There is nothing in the Microsoft support site that mentions this as an
issue. Anyone run across this or happens to know if Microsoft knows about it?

my issue is not exactly like yours.....but am having a similiar problem with
the quantity of pics ......I run the screensaver to choose from pictures in
certain folders......and once that folder has over a certain amount of
pictures.....the screensaver freaks out and only displays one every other
time.......instead it displays the generic picture that is on the windows
photos gallery.....it doesnt do it till my folder has over x amount of pics
in it......so it seems reasonable there is a glitch in the vista
screensaver.........

"Corbism" wrote:

> I've found an issue with the Vista Photos screensaver. I have set as default
> to use images in the \pictures folder. I have roughly 400 images in two
> separate directories in the \pictures folder. The photos screensaver
> displays all the images just fine but, it won't allow my display to turn off
> at time specified in power settings.
>
> I have the screensaver set to turn on at 5 minutes of inactivity. If I have
> the Vista power settings set to "Turn off the display" after say 10 minutes
> or longer, it is ignored. The monitor continues to stay on and display the
> screensaver and never turns off. I tested with the different Photos themes,
> shuffle on and off and different speeds for that screensaver and same issue.
>
> I found a couple of forum threads on other sites from a few months ago that
> show some other people describing same issue. It appeared it had something to
> do with having more than 50 images in the \pictures folders. So, what I did
> was test that and I could duplicate that scenario. I think it really does
> have to do with the amount of images in the \pictures folder and subfolders:
>
> 51 images or more - Display will never turn off at specified amount of time
> 50 images or less - Display will turn off at specified amount of time
>
> Any of the other Vista screensavers do not prevent the display from turning
> off. It's only the Photos screensaver.
>
> I can duplicate this problem on TWO separate systems:
>
> A Desktop (home built) running Windows Vista Ultimate 32-bit SP1
> A brand new Laptop (Dell M1530) running Windows Vista Home Premium 32-bit SP1
> Both computers have latest bios and drivers. The laptop is brand new.
>
> There is nothing in the Microsoft support site that mentions this as an
> issue. Anyone run across this or happens to know if Microsoft knows about it?