Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tiffy]

Win 10 major update 1903 has been released since 10/05/19 I believe and has had some very disturbing reviews, the update invitation has never appeared on my Win 10 PC's until today so I made the assumption that these issues had now been addressed and it would be safe to go ahead with installation.
Unfortunately have wasted a lot of time today finding that this is not the case.

The update takes a considerable time, first thing noticed on completion is that the startup "splash" screen is completely blurred (appears corrupt) regardless of whatever image is chosen.
The desktop resolution appears very poor again regardless of whatever background or resolution is chosen, nothing appears sharp.
Everything is noticeably slower.

I tried the update on both of my desktop PC's producing exactly the came results, not peculiar to one installation, spec's are:
Homebrew Ryzen 5 CPU on a Gigabyte MoBo, integrated Radeon graphics.
Intel i5 Packard Bell PC with integrated Intel graphics.
Both were updated from their existing revision 1809 build 17763.529.
Both running Win 10, 64 bit, Home edition.
There are most likely other issues but I had seen enough and "rolled back" to the previous rev. which thankfully worked without any problems and took a much shorther time than the update.

I certainly won't be updating to 1903 again any time soon.

A recent update of 1809 has already interfered with my local network drives visibility in Win Explorer, something I had a lot of trouble with when running Win 8.1 but was never an issue since changing to Win 10 until very recently, have spent hours and tried every suggested solution available on this, apparently not uncommon !

Will MS ever get their updates bug free before release ? 

[banger]

Updated 2 machines here, very old desktops, the blurred screen sounds like a graphics driver problem. There are a number of known problems which have been fixed with a cumulative update.

Check here to see if the graphics problem is listed, https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903

You could also use the Windows Feedback app to report your problems to the MS developer team.

[jelv]

The blurred splash screen is a feature, not a problem I believe. On the laptop that I updated today, when logged out and totally idle the image is sharp. As soon as I click the mouse or press a key it blurs and I get the login box. If I don't log in, after being idle for around a minute, the login box disappears and it goes back to the normal sharp image. Quite neat I thought.

[banger]

The blurred splash screen is a feature, not a problem I believe. On the laptop that I updated today, when logged out and totally idle the image is sharp. As soon as I click the mouse or press a key it blurs and I get the login box. If I don't log in, after being idle for around a minute, the login box disappears and it goes back to the normal sharp image. Quite neat I thought.

I thought of the Acryllic feature but the OP also says his desktop appears blurred to which got me thinking an on board graphics driver problem, especially if it is Intel graphics.

[tiffy]

@banger:

You could also use the Windows Feedback app to report your problems to the MS developer team

Do you honestly think that would do any good ?

I thought of the Acryllic feature but the OP also says his desktop appears blurred to which got me thinking an on board graphics driver problem, especially if it is Intel graphics

Yes, I know there are reported issues associated with Intel graphics but I have the same situation with my AMD Radeon graphics.

@jelv:

The blurred splash screen is a feature, not a problem I believe

Certainly not to my taste.
I could not achieve a desktop image, colour/graphic combination on either of my VDU's, Dell & Samsung that gave a comparable display to the previous Win version.

The explorer, network drives display issue I had with the previous Win version was certainly not fixed with 1903, this is a very well documented problem which goes back to earlier Win versions and MS have still failed to address, some cynics even believe that it's deliberate to channel users towards their "OneDrive" service as a (paid) network alternative.

[Bowdon]

@tiffy

You've probably done this but just checking. When you got to the desktop screen did you go to windows update again and see if there was anymore updates?

I'm still on an old version of win10 (1803). I was worried about falling behind in updates but most of what I hear these days are bugs and corruptions. The last bug they discovered crippled pc's and people had to roll back. It's not good enough.

[tiffy]

You've probably done this but just checking. When you got to the desktop screen did you go to windows update again and see if there was anymore updates?

Yes indeed, I know it's quite common for "further updates" to be immediately available after a major update.

As already stated, I'am now on revision 1809 build 17763.529, still have the issue with local network drives non-visibility in Win Explorer, that started last week with my MoBo integral Realtek NIC periodically not communicting, got around that by rolling back a Realtek driver rev. (had not updated in the first place), however, the bi-product was the Explorer visibility issue.
My current work around to gain easy LAN, NAS access is mapping all the NAS folders, works quite well but why should I have to do this now ?

It's now got to the stage where any Win update appears to carry a risk, just never completely sure what's going to change, I certainly will be avoiding any future "major" updates until well proven.

[banger]

@banger:
Do you honestly think that would do any good ?

I've had a couple of minor niggles fixed by using the feedback app, they may have been fixing them anyway but worth a shot.

[tubaman]

I've updated my Dell laptop (fairly new) without issue and it didn't seem to take that long. Performance isn't noticeably changed. A much older laptop (Core 2 Duo CPU!) is currently refusing to update - just errors during the first install stage. It is about ten years old so I'm impressed its kept going as long as it has. I will persevere with it when time permits.
I haven't tried my desktop machine (about 6 years old) yet.
 

[g3uiss]

It's now got to the stage where any Win update appears to carry a risk, just never completely sure what's going to change, I certainly will be avoiding any future "major" updates until well proven.

I have my PC set to delay feature updates by 365 and semi targeted. That way I can wait a year until a new version lands before I update. I also have update delay set to 3 as it seems most bad patches are sorted quickly by Saturday of patch week and any out of band get delayed as well.

[parkdale]

At some point during the update, I kept getting failed to update messages. After some pondering on it, I uninstalled Oracle Virtual PC, and all was well.
But upon rebooting I kept getting a 2 boot issue boot once and got a blue screen of death then reboot goes to recovery screen then boot Win 10 on that screen and it boots fine!
This happens every time, so must have been an error with the UEFI boot process picking a corrupted boot path.
But windows recovery would not repair the error, so I booted from a USB with Win 10 ver 1903 and formatted the the UEFI boot partition and then went back to the recovery screen and hey presto we have a repair that works
All is well now with no after effects.

[tiffy]

@g3uiss:

I have my PC set to delay feature updates by 365 and semi targeted. That way I can wait a year until a new version lands before I update. I also have update delay set to 3 as it seems most bad patches are sorted quickly by Saturday of patch week and any out of band get delayed as well.

Sounds like a very good idea, how is this achieved in Win 10 ?

I'am still having isues with my Gigabyte MoBo integrated network, a "Realtek 8118 Gaming LAN" although to be fair the issue started prior to applying 1903 update, ran perfectly for the first 2 months after the PC build then started randomly loosing all ethernet connections even though the Win "device driver" configuration showed healthy all settings as did the Realtek "Ethernet Diagnostic Utility".

Takes a bit of juggling around, disabling/re-enabling, re-booting to restore which will sometimes last for days before recurring, have tried all available drivers, old and new and all suggested on line solutions, there are many recorded instances of this issue associated in particular with Win 10 and the Realtek LAN chip set.

I have ordered up a Intel chip based PCI G.Byte NIC which apparently integrate much better with Win 10, pity I should have to do this with a relatively high spec. modern MoBo (Gigabyte B450M Gaming).
Is the root cause down to Realtek or MS, I'am inclined to think MS as all worked perfectly for the first 2 months and the issue appeared to be triggered by a Win update prior to 1903, can't say exactly which due to the random & intermittant nature of the fault.

[parkdale]

When I looked at buying a new mobo, I made sure that it had a Intel nic and not Realtek, although Intel have had issues in the past. So I bought a Asus H270 prime pro.
Also I have disabled the on-board Realtek sound on my mobo and I'm using the sound output via the disport port on the graphics card because of issues with drivers.

[tiffy]

When I looked at buying a new mobo, I made sure that it had a Intel nic and not Realtek, although Intel have had issues in the past. So I bought a Asus H270 prime pro.
Also I have disabled the on-board Realtek sound on my mobo and I'm using the sound output via the disport port on the graphics card because of issues with drivers.

Yes, had not realised that there were so many recorded issues associated with Realtek network chips & Win 10, still strange that everything worked perfectly with the new build PC for 2 months before I started experiencing network connectivity issues.
Have not had any issues with the on-board Realtek sound chip so far !

This is the Intel NIC I have ordered on Amazon:
Intel PCI NIC
Didn't cost a fortune, hopefully this will solve my issues.
Wonder when the Intel NIC is fitted should I completely un-install the on-board Realtek or just disable in Device Manager, perhaps a un-install would result in a re-discovery/re-enable by Windows as indeed happened a few times @ restart while messing around with my current issue.

Is there a way to get Windows to ignore the on-board Realtek LAN or perhaps it will anyway when the PCI NIC is fitted ?

[roseway]

You should be able to disable on-board devices in the BIOS setup.