[1703, cu] 1703 Lock screen, still no fix?

[Sheridan]

I noticed that a test upgrade to 1703 and the latest cumulative update KB4022725 still haven't fixed the fact the custom lock screen shows as the default MS one and not your own.

 

I know MS removed this option from Pro (out of pointless spite seemingly!) but we use Edu and its still broken.

 

Every day a new 10 problem pushes my planned deployment further back.

[Bankesy]

Good afternoon

 

Just noticed your post scrolling around at the top of the forum and thought I would post that we are using Win 10 Edu 1703 and when we lock our PCs the custom image is displayed although I'm not sure if that update has been applied to our systems.

 

I realise that probably doesn't help you in any way or perhaps I've misread your problem but if there's anything else get back to me.

 

Thank you

[3s-gtech]

http://www.edugeek.net/forums/windows-10/184614-login-screen-background.html

[Sheridan]

We updated some 1607 to 1703 and applied the latest CU, as soon as 1703 went on the default login screen/lock screen is back to the MS one and not ours. Its a well know bug and still seems to be unresolved.

 

Did you install 1703 from scratch or an update? Sometimes that seems to make a difference.

[Sheridan]

Looks like its a 'No' then unless you're prepared to hack around with this mess of an OS, time to roll back to 1607 until 1903 or 2207 fixes the bug....

[Michael]

I can't help but notice Microsoft seem to release a good OS, then a bad OS again -

 

1507 = Good

1511 = Bad

1607 = Good

1703 = Bad...

[Sheridan]

1507 and 1607 were good?!

[Michael]

No major issues my end no.

[Bankesy]

We deploy Win 10 Edu 1703 via MDT if that makes any difference.

[3s-gtech]

Looks like its a 'No' then unless you're prepared to hack around with this mess of an OS, time to roll back to 1607 until 1903 or 2207 fixes the bug....

 

Well, depends on your definition of a hack. I've had to have these little tricks for years, especially on Windows 7 (the folder redirection fail being one of them). Got to be worth a try? I know it still doesn't work after doing this for some, but there's nothing special in use here to make it work.

[Michael]

The lock screen isn't a major issue in my view. It doesn't affect the core functionality of the machine, it's just desirable to have X, Y, Z wallpaper.

 

I'm sure Microsoft will fix it in the near future - so long as you definitely have it working on one machine (saying running 1607), then at least you're covered the setting is correct, but it local or a UNC path.

[mrbios]

I've got my logon screen background setting reliably....so long as you're happy to set an image and keep it at that permanently with no intention of changing

 

I've got two scripts in my sccm task sequence. One which replaces the img100.jpg default image, then another which clears out the S-1-5-18 folder. Windows by default then takes the default windows\web\screen\img100.jpg. Not a solution by any means, but enough of a workaround to keep me happy.

 

Only very basic batch scripts:

TAKEOWN /F C:\Windows\Web\Screen /R
ICACLS C:\Windows\Web\Screen /grant:r Administrators:F /T
ICACLS C:\Windows\Web\Screen /setowner Administrators /T
DEL /F /Q C:\Windows\Web\Screen\*.*
COPY /Y "\\sccm\sources\Applications\Windows 10 1703 Lock screen settings\Lockscreen1.jpg" "C:\Windows\Web\Screen\img100.jpg"

 

and

 

rem ------ loosen permissions on a single folder in the path where the cached images are kept
takeown /F C:\ProgramData\Microsoft\Windows\SystemData
icacls C:\ProgramData\Microsoft\Windows\SystemData /grant:r %UserName%:F
icacls C:\ProgramData\Microsoft\Windows\SystemData /grant:r Administrators:F
icacls C:\ProgramData\Microsoft\Windows\SystemData /setowner Administrators


rem ------ loosen permissions on the sub-folders where the cached images are kept
takeown /F C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18 /R /D Y
icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18 /grant:r %UserName%:(OI)(CI)F
icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18 /grant:r Administrators:(OI)(CI)F
icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18 /grant:r SYSTEM:(OI)(CI)F
icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\* /inheritance:e /T
icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18 /setowner Administrators /T

del /Q C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen*

 

Can't remember where i got them to give credit...

[tmoon-mint]

I was under the impression the latest cumulative update resolved this issue. Seemed to apply the lockscreen for me once the machine was fully updated.

 

Microsoft Update Catalog

[Sheridan]

In the registry delete fix mentioned, the correct path to our custom lock screen is in there (GPImagePath) - is that how you found it?

 

Even thought the path is correct and the file is there it still shows the MS default.

[Sheridan]

I applied KB4022725 as its the latest one after 4020102, maybe that breaks it again!

[HereIGoAgain2601]

We installed an update as per one of the other posts on this forum and it solved the issue. KB 4020102

[3s-gtech]

I've found that the May CU didn't fix it alone, which is why I had to delete the cached settings in the registry. It does pay to try setting the lockscreen image as a local file rather than UNC, although UNC worked in 1607.

[Sheridan]

We use a locally copied file as the lock screen - worked OK in 1607. Our registry entries are correctly pointing to the local file which is why I haven't deleted them yet - did yours show the correct path/file before you actually removed them?

[3s-gtech]

Yeah they did, but it still didn't work. It was the action of deleting them and restarting them that kicked it in. Bear in mind you may see a plain blue screen for a few restarts, then it seems to work fine afterwards.

[Sheridan]

Hmm if thats the case I might try a complete fresh install of 1703 with the latest CU and then apply the group policies and see if that works. Applying 1703 as an update takes longer then reimaging anyway.

[3s-gtech]

That's true. I've heard that if you build 1703 with the latest updates, then add to AD, the lockscreen GPO will apply without any hacks.

[Sheridan]

Re-imaging 1703 from scratch now to try it out!

[HereIGoAgain2601]

I have it working on in place upgrade and a fresh image so long as the update is installed KB4020102

[3s-gtech]

That's the May update - does it still work for you with the June ones applied?

[alfatec]

Well, downloaded the latest 1703 ISO from VLSC. Built a fresh image with just 1703 on it. Did Windows updates from Microsoft online and not WSUS which brought it up to date with the latest CU. Placed an image in C:\Windows\Web\Screen and changed group policy

to reflect it. Only applied the 'Force a specific default lock screen and logon image' policy under 'Computer Configuration'. All I get is a Microsoft default blank blue screen, as soon as I remove the policy it goes back to the standard Microsoft Cave photo so I know the

policy is being applied. Did exactly the same on a 1607 workstation and all works fine. Latest 1703 policies also uploaded to Active Directory. Come on Microsoft stop appeasing to the home users and give corporate users some support.