SCCM 2016 - Windows 10 OSD - Task Sequence - finishes with black screen & cursor

[andyire]

Hi All,

 

I am getting a black screen with cursor after deploying Windows 10 OSD SCCM task sequence. Not certain what the cause is. If anyone has come across this issue or similar, would you mind sharing your solution ?

 

 

Background

 

OS Version - Windows 10 - 1803

SCCM 2016 - CB (latest Update)

ADK - Latest Version

Boot Image (x64) - latest version - imported from ADK

 

 

---

 

 

I have created a OSD Task Sequence in SCCM, with the basics -

1) Partition Disk

2)Apply OS

3)Apply Windows (I have specced an unattend.xml)

4)Apply Network (basic DNS & domain extension)

5)Apply Drivers (have enabled - unattended install of unsigned drivers)

5) Setup Windows & ConfigMgr (have set SMSMP, DNSSUFFX, SMSCACHESIZE)

6)Install Applications (setup as packages rather than Applications)

.Net 3.5

Chrome

Impero

Google File Stream

VLC

7-zip

 

 

The process appears to complete without errors, however the computer gets stuck on a black screen with just a cursor.

 

If you force the computer to switch off using the power button & then power it back on again, the PC continues fine.

The OOBE appears and goes through (doesnt ask for anything due to the unattend.xml) and then drops you at the Windows Login screen.

 

Once you login, the applications have installed fine & all the correct drivers appear to have been picked up.

 

Looking in Event Viewer - I can't see any obvious errors.

 

 

The smsts.log does show a couple of yellow flags, as follows, but I haven't been able to pin down if they are relevant

 

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram

 

GetTsRegValue() is unsuccessful. 0x80070002.

 

 

 

Thanks in advance for any suggestions.

 

Cheers

 

Andy

[azureusnation]

Would you be kind enough to zip up the client logs and send them over to me. I can then have a proper look.

[FishCustard]

0x80070002 is 'file not found', so I guess it can't find that registry key. Might help troubleshooting.

[snagrat]

Used to be a bug where you would need a reboot action after the Setup Windows and ConfigMgr step.

 

Try adding a reboot step

[andyire]

HI All,

 

Thanks for your replies. Back to work from a few days off. Decided to remove all packages and re add one by one. Black screen seems to have gone away now, so it must be a compatibility thing between one of our packages and 1803 which didnt exist when using 1709.

Not totally resolved yet but slowly getting there,

 

Cheers

Andy