Windows 10 1809 - Issues after upgrading

[craigcamacho]

Hi Guys,

 

Ok so recently ive deployed an upgrade package using SCCM to upgrade my 1709 machines to 1809. I injected numerous updates into the wim to bring the version up to 17763.348 because the version on our VLSC is still an older version which when deployed happens to break mapped network shares as well as many other things. Since the upgrade we have been experiencing some really annoying issues. The first one is just general slowness of the machines with things like login times and laggy start menu and the next issue is after a user has logged in they will get a black screen with a cursor. The black screen issue seems to be random as hell and ive had a member of staff log in first thing in the morning and its fine then come back a few hours later to the same computer and he gets the black screen. I have trieda few things to try and fix these issues such as disabling fast startup, disabling the app readiness service, disabling delivery optimisation for Windows Updates, updating the graphics drivers to the latest ones. I never had any of these issues with 1709 and the issues only started when 1809 was installed. Has anybody on here come across these issues and if so what did you do to resolve the issues? Please bare in mind ive over 700 computers so visiting each one individually to manually fix isnt an option.

 

Also am i the only person whose patience is wearing thin with Microsoft and their s****y updates and CB upgrades and the fact they dont seem to test jack s**t anymore?

 

***note*** after disabling the app readiness service it seem to break our Office 365 SSO so i changed it back to enabled.

Edited March 13, 2019 by craigcamacho

[mavhc]

Not noticed many problems when upgrading to 1809, from 1803. Kyrocera printer driver does BSOD on some fonts, which isn't good. One desktop in my IT room has black screen for ages when logging in, I reimaged it.

[Arthur]

Do you use Impero?

 

www.edugeek.net/forums/windows-10/196616-black-screen-cursor-new-image-2.html#post1697644

[mavhc]

Black screen that fixes itself in the end, or black for an hour?

[craigcamacho]

Thanks for this i think you might be right as looking back it does seem to be all the rooms that have Impero that are complaining. Ive already contacted Impero regarding releasing the latest version to us and which exceptions to inject and which AV exceptions to setup etc. I will get all this sorted and report back as to whether its resolved our issue or not. Thanks again for this suggestion I totally had my Windows blinkers on and Impero hadnt even crossed my mind.

[Fazza]

Thanks for this i think you might be right as looking back it does seem to be all the rooms that have Impero that are complaining. Ive already contacted Impero regarding releasing the latest version to us and which exceptions to inject and which AV exceptions to setup etc. I will get all this sorted and report back as to whether its resolved our issue or not. Thanks again for this suggestion I totally had my Windows blinkers on and Impero hadnt even crossed my mind.

 

If I remember correctly, there is some sort of configuration/setting change you have to make in Impero when going from an old OS like W7 to a modern OS like W10 - something to do with ignoring a particular file that is part of Windows 10 and not 7 I think.

[Arthur]

Thanks again for this suggestion I totally had my Windows blinkers on and Impero hadn't even crossed my mind.

Due to the way Impero works, it's always the first thing I check.

[craigcamacho]

Ok guys so its been just over a week since i updated our version of Impero and configured all the recommended AV exclusions etc and everything seems to be fine now. Many thanks for all your help and suggestions on this guys.