[1703, cu] Windows 10 - Missing Text

[Fazza]

After installing Windows 10 1703 from scratch, installing all our software I then created an SCCM image and deployed it (along with some drivers) to a test PC from a computer suite.

 

On logging on this happened:

 

 

 

No text!

 

I re-imaged the PC with the VGA driver removed and it worked OK when I logged on but as it had the Basic display adapter driver I installed a different version of the graphics driver which worked OK so I added that to SCCM and re-imaged the PC.

 

After re-imaging with a different VGA driver it all worked OK. Or so it seemed... as I was testing the redirected Start Menu, on one reboot I logged on and had no text! Logged off and back on again and the text was there again!

 

The PC is an i5 4440 with 4GB of RAM on an Asus H81M-C motherboard with a 120GB SSD HDD.

 

Any ideas what is going on?!

[ZeroHour]

Do you use any pc monitoring software like Impero etc? I know there have been some issues people think may have been caused by older versions.

Also try adding a different language pack in using settings, remove english uk, reboot then readd and switch back.

[Arthur]

www.edugeek.net/forums/windows-10/183619-windows-10-v1703-missing-text-3.html#post1585346

[Fazza]

Do you use any pc monitoring software like Impero etc? I know there have been some issues people think may have been caused by older versions.

Also try adding a different language pack in using settings, remove english uk, reboot then readd and switch back.

 

We use Impero (for our sins).

 

www.edugeek.net/forums/windows-10/183619-windows-10-v1703-missing-text-3.html#post1585346

 

I searched the forum and missed that one! Thanks for the link. Impero mentioned again I see.

[Arthur]

Impero mentioned again I see.

Whenever there is an issue, Impero is *always* the first thing I check. It's a shame because it never used to be so problematic.

[Fazza]

Whenever there is an issue, Impero is *always* the first thing I check. It's a shame because it never used to be so problematic.

 

It's not Impero that has caused this issue though as it's a change in the OS that has caused it and if we had been on the very latest version this wouldn't have happened as it's been updated to work with 1703.

 

I do know what you mean by 'problematic' though as the reason we're not on the latest version is because we've lost a lot of faith in them over the last few years. Maybe now they've got some investment in the business they might improve going forward.

[sparkeh]

Hmm I think we have the same motherboard and I have come to believe that v1703 has some issues with some Intel graphics drivers but haven't quite got to the bottom of it yet.

 

We are seeing some odd results with imaging machines, for instance one issue is that during OSD it won't pull down the drivers from the sccm server yet after OSD it will connect to Windows Update and grab the exact same driver. Works fine with 1511 and 1607 but not 1703.

[ZeroHour]

The fall update is out this month so it may be worth seeing if that helps. I know creators did have issues with certain drivers as they had changed something video related.

[Fazza]

The known Impero issue fix of adding an exception hasn't worked. I'm now in the process of upgrading to the latest version as we're a little out of date so we'll see if this helps. No pressure but the computers have got to be up and running by start of play Tuesday!

[Ephelyon]

Have you seen the last post (by me) in the thread referred to earlier? You may need to add dllhost.exe as an exception as well as fontdrvhost.exe to get it to work properly...

[Fazza]

Have you seen the last post (by me) in the thread referred to earlier? You may need to add dllhost.exe as an exception as well as fontdrvhost.exe to get it to work properly...

 

I did that and that did not resolve the problem. Infact the more I rebooted the machines the more computers were affected with the issue of missing text.

 

The changelogs from Impero suggested this 'issue' was fixed in later versions of the software that was compatible with Windows 10 so I upgraded to the latest version and *touch wood* it seems to be working OK now.