Microsoft confirms 2 new Windows 10 version 1903 upgrade blocks
Microsoft removed three upgrade blocks from the list of issues affecting upgrades to the company's Windows 10 version 1903 operating system.
We noted in yesterday|s article that users were facing new issues that Microsoft had not confirmed officially at the time even though they appeared widespread enough to warrant at least an entry on the bug tracking list.
Microsoft confirmed two new issues on July 12, 2019 that the company considers serious enough to block machines affected by these issues from upgrading to Windows 10 version 1903.
One issue affects Surface Book 2 devices exclusively, the other confirms the reported Remote Desktop black screen issue.
Surface Book 2 issue
Microsoft confirmed an issue affecting Surface Book 2 devices that causes certain graphics intensive operations to fail on the device after upgrading to Windows 10 version 1903
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Window 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open.
Microsoft suggests that administrators who upgraded Surface Book 2 devices to Windows 10 version 1903 already restart the device when that happens or run a manual scan for hardware changes in the Device Manager instead.
Remote Desktop Black Screen issue
The second confirmed issue affects devices with certain Intel 4 series chipset integrated GPU hardware to which remote connections are established. The issue may occur to any device initiating the remote connection and users may notice that the screen remains black once the connection is established.
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).
Microsoft offers no workaround for the issue at the time but Günter Born published a workaround on his site some hours ago that might resolve the issue.
Apart from upgrading graphics driver on affected devices if possible, Born suggests that administrators disable the use of the WDDM graphics display driver for Remote Desktop connections in the Group Policy found under Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment.
Now You: are you affected by these issues?
Does anyone on Microsoft know what is doing? I have 3 VPN connections for professional daly use, and now cant use either… WTF??? last update couldn´t find any PC on my office… please send the kids away or call to the older microsoft employees to teach the new kids. for god sake!!!
The big problem may be with Remote Desktop Connection and with the brightness, other are not that important, not many people or companies have Surface Book 2, but i’am sure they will fix all of this.
For the normal user/people can be a problem Windows 10, but just because they don’t call for a IT technician, to install/preinstall windows and to configure it properly.
There are a few tricks to make-it work and look like Windows 7, it is not like Mac OS that you install with 2 clicks and thats’it.
So my recommendation is CALL an IT GUY, or switch to Mac OS.
Windows 10 is a disaster and it is getting worse and worse. I have the feeling sheep and donkeys are working in Microsoft.
I despise Windows 10, truly, absolutely despise it. I have honestly never been so consistently infuriated with a Microsoft OS.
And it only keeps getting worse over time. If you would have told me years ago that soon we’d have freaking advertisements and spam in our start menus, I would have laughed, thinking it was a kooky Black Mirror-like dystopian what-if scenario, but couldn’t imagine actually happening (or at least us users allowing for it to happen, not that Microsoft wouldn’t want it). And yet here we are.
Why am I blocked from signing in to Windows by GitHub after I updated?
Just no listen from Microsoft is need change clean system from full bloatware and make check options what is need install apps and enable feature options how holographic or others apps… For now is bloatware full with bugs.
windows 10 < windows me. Seriously m$ is self destructing in front of our eyes but few are paying attention. we need an admin revolt against this garbage os that comes out with a new set of problems with each feature update, its a dumpster fire. I'm nostalgic for the good old days of SPs.
Dilly dilly, theres little to no choice except linux or unix. Yeah thers Apple, but the billions of dollars it would take to switch over and test tons and tons of apps….not likely. To bad MS needs a serious competitor.
Would totally agree.
I just decided to ride out Win 8.1, there’s a possibility of switching to Mac OS later if reports about Catalina are mainly positive. Mac users in my family have had some issues on Mohave but with Windows on it’s constant downward spiral and increasing telemetry being directly tied in to basic OS functionality, a change is pretty much imminent.
There aren’t too many reliable consumer grade operating systems out there as I’m beginning to find out.
I’ll give props to Martin for bringing someone in (Ashwin) who’s been exploring other systems, here’s hoping that a future write up on Mac OS & hardware are in the offering. (impartial reviews & not MacWorld type shrilling..)
I don’t know if anyone else has mentioned that UPS Worldship is also a barrier to upgrading to 1903. Right now the only known solution is to backup the database, completely uninstall the software, upgrade to Win 10 1903, then reinstall the software. I’ve called UPS support twice, the first time they acted like it was the first time they ever heard of it. The second time, last week, they basically said they know about it, and they had no suggestions other than to not install 1903. Here are two links I’ve found on it: https://www.reddit.com/r/sysadmin/comments/bunlnd/fyi_ups_worldship_2019_and_windows_1903/
https://answers.microsoft.com/en-us/windows/forum/all/ups-worldship-on-windows-10-1809-does-not-work/f04ca7d8-58a0-45fa-b807-002f2c519351
It’s bad when you can’t even get your own devices to work with the OS properly.
If they move on in the right way, probably no other Windows OS will be worse than W10.