Windows 10: Slideshow Problems W10 ASUS

Before I begin to list the problems I have had with the damned Slideshow, I need to explain why it came about.
My laptop is an ASUS ROG G751JL and of course it has bloatware on it. I accidentally ran "ASUS Screen Saver" which COMPLETELY CHANGED ALL MY SCREEN SAVER SETTINGS. I have not been able to get it fixed since then. I use to have my setting that would go to my lock screen folder of photos that was set to change every 5 minutes. After I did this stupid thing by running that bloatware application, the 5 minute option stopped working. Now it has taken all of my options. It will go to my lockscreen background but not run the slideshow part of it and this is only when I set it to 1 minute photo changes. When 3 minute photo changes is on I just get a black screen.

Things I have done to attempt to fix it without any solutions,
- Changing all my battery settings and redoing them
- Changing all my lock screen settings
- Removing and re-adding my folder of photos
- Used REGEDIT to change ASUS's screen saver registry from 1 (hexa) to 0 (hexa)
- Trouble shooted by using System Maintenance with Admin privileges

I literally have no idea what is going on with this.

:)

 

Windows 10 Small Freezes/Hiccups/Lag Spikes

I had the same problem. After hours of disabling processes and services and updating drivers I realized it was happening every time the wallpaper changed... disabling the slideshow fixed it for me... really Microsoft? As if the sound bugs weren't enough
simply having a slideshow active is making my laptop borderline un-usable. You really needed to do a lot more QA before releasing this version of Windows.

1. I upgraded from Windows 8.1 by the automatic Microsoft downloader

2. I have an ASUS laptop: ASUS G750JZ-DB73-CA

 

Windows 10 dual monitor lockscreen problem

Hi, just upgraded to W10. W8.1 played a slideshow on my lockscreen on both of my monitors. W10 only plays it on one, the other is black which looks pretty bad and isn't ideal.

Anything I can do about this?

 

How about doing a System Restore to a date and time before you did this? That should fix it.

 

I don't have a system restore created before that happened.

 

Start by running sfc /scannow from a Elevated Command Prompt.
If correctable errors, follow these directions:

SFC SCANNOW and DISM RESTOREHEALTH - Repair Corrupt Files