Here’s a list of the major known bugs in Win10 version 1803

Topic

New Reply

Note that I didn’t say “short list.” Post coming in Computerworld.
[See the full post at: Here’s a list of the major known bugs in Win10 version 1803]

1 user thanked author for this post.

Fred

Reply | Quote

Replies

Glad I didn’t fall for the Check updates trap-After I read the articles, I’ve strayed AWAY from checking windows update to check the update history. When may 8th comes around, I AM HIDING THE 1803 update that comes out on windows update. But again THIS HAS become a BIG mess for 1803 from the get-go.

Reply | Quote

Woody, ‘And an anonymous poster then confirms that these settings are turned off in 1803, on a VM: BTIDisabledBySystemPolicy, BTIDisabledByNoHardwareSupport.’ Well, it’s not your fault that you got it wrong (in this case, ‘False’ has no meaning because BTIHardwarePresent, BTIWindowsSupportPresent, and BTIWindowsSupportEnabled are ‘True’). But yeah, reading Microsoft’s docs have always been a guessing game.

Edit to remove HTML

2 users thanked author for this post.

Great Lake Bunyip, woody

Reply | Quote

The most irritating 1803 bug for me has been the loss of “Stereo Mix” so I can output sound to two devices. I’ve had to redo it twice now.  v1803 supports it, but the update apparently doesn’t carry the setting forward from the previous version.  I upgraded because v1703 was becoming unusable.  Also setting a metered connection when I don’t really need one caused problems for other apps, notably Outlook 365 and Amazon Music.  Both are working well now.

2 users thanked author for this post.

Great Lake Bunyip, woody

Reply | Quote

I installed so I can test the update before rollout to our users machines. I test general stability, hardware compatibility, and app compatibility plus general everyday usage. On iur Dell optiplex 3020, 3040, 7020 and Latitude E5440, E7450, E7470 machines that I’ve tested I’ve not run into a single problem with the update.

I use GPO to control when the update occurs so anything not in my test OU has major updates delayed.

Reply | Quote

“Frequently, with new Win10 versions, it takes a week or two for the big problems to present themselves”

Since MS pushed 1803 aggressively onto seekers, the number of upgraders within the first week or two are likely to be considerably higher than usual, so it isn’t too surprising that the big problems presented themselves almost immediately this time.

Reply | Quote

Reading on Intel graphics forum that the Chrome issues and other freezing may be due to Intel drivers specifically with 620/630 graphics. Intel, Google, and Microsoft working on may 8th fix.

Reply | Quote

I have HP EliteBook 820G4 with Intel 620 GPU. Upgrading to 1803 via .iso downloaded from MSDN at 1.5. broke my GPU. The solution was to downgrade drivers to a version released about a year ago. The latest drivers didn’t help.

Otherwise, we have 6 computers upgraded from 1709 enterprise to 1803,  and no big issues found thus far. My colleague lost his desktop wallpaper, but I wouldn’t classify that as a big issue.

-Olli

Reply | Quote

Wow! I was really counting on 1803 being a good rollout so I could upgrade pretty quickly, since I’m sitting on the now unsupported 1607. Doesn’t look good for my much desired 18-month upgrade schedule so far. I’ll be watching closely and hoping this mess can get cleared up enough very soon so Woody can give us the thumbs up to upgrade if we want. On the other hand, 1803 offers nothing I want or need, but I can’t continue very long on an unsupported version. Doggone it!

Reply | Quote

Hope springs eternal.

1803 may turn out to be good, maybe, but it’s going to take a while.

3 users thanked author for this post.

Great Lake Bunyip, columbia2011, dononline

Reply | Quote

So upgrade to v1709. It’s gotten pretty solid.

NEVER assume you can upgrade to the latest version when it first comes out.

-Noel

5 users thanked author for this post.

columbia2011, Great Lake Bunyip, Seattle27, BobbyB, dononline

Reply | Quote

That’s definitely being seriously considered. I’ll give it a while yet, though. I sure had my heart set on sticking with an 18-month upgrade cycle.

Reply | Quote

I don’t usually get the new updates because I have an older machine, but this time when checking updates, 1803 was there and it began installing. I have Windows Home version so there wasn’t anything I could do to stop it.  I was hopeful though, since I’ve never had any issues with the updates. This time was different as I began experiencing the 1803 freeze – totally unrelated actions occurred just before it froze – not sure if there is a common denominator – Chrome was open but I wasn’t using it at the time. I easily rolled back to 1709 with no problems except that the machine wants to update to 1803 again. Since I have Windows Home the only thing I could think to do was set my Wi-fi and Ethernet to metered and disable the Windows Update service. I’m now waiting until I hear positive results from the 1803 fix that is to come out May 8 before I turn updates back on. I don’t like operating this way, but it’s the only thing I could think to do with these forced updates. That’s my story.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Yep, metered connection is your only hope.

https://www.computerworld.com/article/3232632/microsoft-windows/how-to-block-windows-10-april-2018-update-from-installing.html

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Par for the course for MS update/grade these days, bugs everywhere. I am just a home user so I feel comfortable with updates ‘OFF’ altogether until I see a few green lights.

It’s gotten so bad with Win 10 it even makes the front page of an international news site in Australia https://www.theguardian.com/technology/2018/may/04/windows-10-april-2018-update-bug-locks-machines-running-chrome-cortana and then disappeared – how the news is controlled.

1 user thanked author for this post.

dononline

Reply | Quote

As of the date and time of this post, the article you refer to in the Guardian is available again. Nice write up of theirs.

Reply | Quote

https://www.windowscentral.com/windows-10-april-2018-update-common-problems-and-fixes#fix_blackscreen_problem_windows10_1803

There are a ton of April 1803 Problem Fixes in this article (a lot toward the end you’ve discussed in AskWoody).
Clarify and use as desired.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

I saw that. Some of the “solutions” are fixes proposed by Microsofties. Others seem to be untried. I was going to write about them, but figured it’s all going to change today anyway.

Let’s see what MS fixes on Patch Tuesday.

Reply | Quote

Chrome freezes

It’s certainly not a surprise. Think about it… Why on Earth would Microsoft keep their OS compatible with THAT?

You can’t honestly think that in the halls of Redmond they didn’t notice it would freeze up the most popular browser on the planet… Even the junior engineers would test THAT.

With Microsoft, never attribute anything to incompetence that can be ascribed to marketing.

Microsoft’s response will of course be, “Oops, sorry.”

-Noel

4 users thanked author for this post.

BobbyB, Elly, Great Lake Bunyip, dononline

Reply | Quote

But Edge/Bing/Cortana will gain market share in the mean time!

2 users thanked author for this post.

Noel Carboni, dononline

Reply | Quote

Nah, most will revert back to v1709 and then use Chrome

Windows - commercial by definition and now function...

2 users thanked author for this post.

Noel Carboni, Elly

Reply | Quote

To be honest, it’s 3rd party software. And not the only one of the planet to serve its purpose. I’d prefer Google to adapt to the new OS than the other way round.

I personally use Firefox and IE11 (for Silverlight), so I haven’t really noticed.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

Hello Woody, another problem 1803 had was with Firefox but they fixed it quickly.

https://www.mozilla.org/en-US/firefox/59.0.3/releasenotes/

https://www.mozilla.org/en-US/firefox/52.7.4/releasenotes/

“Fix for compatibility with Windows 10 April 2018 update (Bug 1452619)”

Reply | Quote

OK, first the reason i installed 1803: i like to run updates when conveninet for me, i feel they will be more secure and my past win 10 updates have gone well.

My PROBLEM with 1803: Installed fine, seemed to be working fine.

THEN i ran Advanced System Care, Short story: Both Deep Optimization and Junk File cleanup seem to hose your system -Win 10 hang during boot-up. The fix involves rolling back to prior version. INCREDIBLE time consuming headache. SO either do not go to 1803 or do not use ASC.

1 user thanked author for this post.

woody

Reply | Quote

Edge crashes when pasting a URL in favorites

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Why did I upgrade? Because it’s like eating ghost peppers. An exhilarating experience, I’ll either die or flush my tear ducts

I upgraded my kids and grand-kids machines so they can report any issues before my clients start calling. So far on a few older Dells no issues reported… yet!

1 user thanked author for this post.

Sueska

Reply | Quote

I install every new Windows update right away, because some user somewhere in my world will do it and demand help.  So far no issues.

Reply | Quote

For me, eliminating the homegroup is great. I checked win update and it installed 1803. So far I haven’t run into any issues I actually use but have been able to duplicate a few that involve my system. Most are too specific and my stuff is all generic, I build my own. I think that may be why I don’t get issues with these updates. Currently, I am not allowing the other system to migrate to 1803.
Sadly, this means I have not been able to test the (new?) networking feature (?) though it reads as if they are going back to what worked all along.

Work systems are all still on win7. Knowing 10 is important because work will be migrating at some (rapidly approaching) time. I won’t have the ability to control upgrades on those. I need to experience the flow and fail of these processes. Better to do this at home with a spare system available than to struggle with it in front of our customers.

Reply | Quote

Firstly, my experience with the OS after the upgrade.  1) I was getting nagging “Low space” warnings on a Drive D: that didn’t exist before.  This “new” D: drive I suspect was the OEM Recovery partition that somehow became exposed and mounted as a regular drive. I figured out that these warnings came mostly from File History and Backup and Restore (Windows 7) trying to do their thing to the tiny “new” Drive D:, instead of working with my backup drive, which had been reassigned to Drive F:.  Fixed with DISKPART, first by removing the drive letter assignment to the “new” Drive D:, then reassigning the Drive F: backup drive the now freed drive letter D:. 2) Some games I play will claim they can’t find my video drivers…”no video drivers” are installed. Seeing that both Intel 4600 integrated graphics AND a nVidia GeForce GTX745 discrete graphics hardware is present…anyway, rebooting has so far fixed this.   THEN I found out that I could do the same thing by disabling then re-enabling the nVidia card…seems that a particular nVidia driver version had it’s own bug.  I tried this remedy once…I don’t recommend it because the 6 second duration of BLACK screen is scary, especially when you can still hear system activity sounds…VERY scary. 3)  On occasion…and I’m emphasizing NOT on every instance, the system “hangs,” either on a black pre-splash screen or on Alienware’s “alien head” splash screen on a “soft reboot”…by hanging I mean more than ten minutes of just waiting to see if something changes before I try to boot it again.  Mostly, [Ctrl]-[Alt]-[Del] will recover from that, but a handful of times I’ve had to resort to a “hard boot”…turning off the power via the power switch, waiting a couple of minutes, and turning on the power again. 4) Universal (UWP) apps tend to start crashing about the same time, the kind of crash where the window just disappears without a sound or sign of complaint, and you wonder what the heck happened; I’ve taken those close-together crashes as a sign I need to try a reboot, almost as if something in the kernel is flapping like a loose high-pressure water hose, spraying bits all over a contained compartment.  I think of this analogy because the Win32 apps seem to be pretty much unaffected by crashes, though they can have other strange behavior, mostly like buttons seeming to be clicked twice, and mouse wheel scrolling going wonky.

Now, as far as your question as to why I went and pulled the trigger on updating now, instead of waiting to do it later.  My answer is two-fold.  One is that I’m still waiting for Dell to release a new UEFI/BIOS for my rig…a Haswell family Alienware X51 R2.  As far as I know, the most current BIOS is A12, which was put out just before Meltdown and Specter hit the vulnerability scene.  So, I had reasoned that since Microsoft had said it would take a hand in getting out mitigations in microcode to guard against the weaknesses, I had assumed, apparently in a mistaken fashion, that said protective code would be in the April Update.  The second reason is much more mundane…there is an element of “RED Button…push only when the situation is DIRE” in reading and hearing about new Windows features like Timeline and the higher number of pinned People favorites (five in 1803 vs three in 1709).  Remember the young really nerdy geek guy on the sci-fi show “Eureka” how he had the thing about turning keys and pushing buttons, even when warned not to do those actions?  Like, a powerful and irresistible urge to see what happens.  Well, I can be a bit like that, even at my age.

Besides, I figured that this time, I would have a chance of getting any bugs fixed by the ‘Softies before my time is up to roll back.  I performed the upgrade on May 1st, the last day to bail out back to 1709 is May 10th, as I understand it, and the first Patch Tuesday is May 8th.  RED Buttons are insidiously sexy…like calling out with a siren’s song… I know, one might get me in the end, BBUUUUTTTT… *rueful laugh*

And there you have it, me and mine in a nutshell.

1 user thanked author for this post.

columbia2011

Reply | Quote

http://sdbr.net/windows-10-update-failure/

1 user thanked author for this post.

BobbyB

Reply | Quote

http://forum.notebookreview.com/threads/xps-15-9550-i5-windows-will-not-complete-installation.802745/

Reply | Quote

And he was fairly computer literate… what about the regular people that happens to?

He did an update at the bottom of the article saying that Microsoft was interested in the logs so they could problem solve…

It can’t be said too much as far as I’m concerned… using home users as beta-testers is in no-one’s best interest. The amount of distrust and failure is giving Microsoft a bad reputation that no amount of marketing can overcome.

Non-techy Win 10 Pro and Linux Mint experimenter

4 users thanked author for this post.

dononline, Cascadian, Microfix, BobbyB

Reply | Quote

The Dell XPS 15 9550 came with Win 10 preinstalled in fake-RAID mode using the proprietary Intel RST driver on a hybrid SSHD(= a hard-drive that contains both a 32GB SSD as cache and a 1TB HDD for the OS) = very fast disk performance.

Such a “weird” computer configuration will often encounter problems when forced auto-upgraded by M$ twice-a-year.

Even doing a clean reinstall of Win 10 on such a computer is a problem.

Reply | Quote

Again, after the update of Lenovo Yoga 2 tablet, touch stopped working. So, again, OTG cable & chipset driver reinstallation. It starts to be annoying. Luckily I have the cable.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

For those of you who run Home networks, life with 1803(4) is going to get a little fraught. Obviously Home Group is gone and if you have 2 x 1803(4) machines on your network your going to hit problems with windows networking.
Spent Friday afternoon and most of today on a mixed bag of 15 machines Win’s7 to 10 vers 1607, 1703, 1709 (work group not Domain) and no problems with all except 2 x Win10 1803(4) yeah they both see each other but that’s as far as it goes, and yes file sharing was enabled; The dreaded 0x80070035 network path not found. every time despite, here goes on both machines:-
Firewall on\off
SMB1.0/CIFS on\off
Network Reset (priceless going old and grey watching that one at 5 mins a time on both machines)
All network services enabled (too many to list inc Function Publication etc)
(If memory serves me right it looks like the settings in services for Home Group have gone also)
NetBIOS over TCP
Assigned static IP’s and or DHCP
Drivers needless to say, although all the other machines have no problem
Just for good measure known good network cables and a spare router, same deal
LanMan Reg key set to “0” (actually was already “0” apparently by default)
Even tried setting Master Browser Reg key in various permutations of the two affected Machines knocked one or two machines out but, “Nada”
Reliable Multicast Protocol, installed
Ton of CMD’s to numerous to list, \\TestNet etc, Ping, pathping etc, nbstat -b etc
Just for fun ran all Win ever so helpful bundled network Diagnostic goodies, all reported everything was cool, errrrm obviously not!
Anyone else seeing this problem??
Well that was a day and half well wasted at work, couple of machines that had to go out Monday went out with 1709, hooked up to the network no problem and thus despatched.
It could be a real chore if anyone’s running a Home network, as for me well 1803(4) aint going anywhere near my machine(s) why mess up a working network, and have to fix it for free

PS and to sum it all up my co-worker declared, “man even solitaire S**ks” and indeed it does on 1803(4)

1 user thanked author for this post.

columbia2011

Reply | Quote

Hasn’t Solitaire been “broken” with each Windows version? I always used to port the old, original one over to each new win editions…

Apart from that important issue, wonder if this may help your network question? https://www.ghacks.net/2018/04/17/fix-pcs-no-longer-recognized-in-network-after-windows-10-version-1803-upgrade/

But why isn’t getting a group of pc’s to work together the easiest thing in the world with newest Windows???

Reply | Quote

“All network services enabled (too many to list inc Function Publication etc)”

Yeah its my habit of abbreviating stuff and trying to think what I did at the same time.
Many Thx young Jan all help is gratefully rec., well apart from still tearing my Hair out, and there’s plenty of it for now, I am just waiting to see if, “Horror of Horror’s”, if the new Cumm UD brings any relief. Cant believe I am even contemplating doing this on a patch Tuesday. But “c’est la vie” or “any port in a storm”.
As for Solitaire being, well to say the least, “Jerky” and slow. It still works although its painful to play, and was the epitome of a day and half’s “time wasted” lol
You certainly need a sense of Humour with “Windoze”

Reply | Quote

Many Thx young Jan…

Blushing and giggling like a little school girl now!

My boss sometimes calls me both boy and lad, but with his 89 years he of course pales my mere 63!

Happy problem solving! You could of course update everything to 1803…

1 user thanked author for this post.

BobbyB

Reply | Quote

Maybe MS broke Home Networking so you would have to use their Cloud to accomplish the same thing.

Reply | Quote

Hey you know you could be right lol, soon got tired of “scooting” the chair back and forth across the room clutching a USB stick. Just threw everything on to “One drive” (which still mercifully doesent turn the Machine over to the evils of an M$ account…Yet!) Well its a test setup of all the versions and machines we use and\or send out in the field. Thank goodness its not up 3 flights of stairs, one way I suppose of losing a bit of weight.

Reply | Quote

UPDATE

Finally fixed by a tip on an obscure web site “Wozhub” the link and page evades me suggested a little unlikely fix, for the 1803 Networking woes. It was as simple as Disabling IPV6. Yeah that’s it one box unticked. Control panel->Network and sharing centre->Network Adapter(Access type connections:)and untick IPV6. You’ll have already been in there if you have enabled NetBios over TCP and\or Installed Relaible MultiCast Protocol Especially useful this tweak if your on an ISP that’s not quite there with IPV6 or your router doesent support it. Probably the quickest and least painful Networking tweak to try first off accompanied by a reboot. Function Discovery in Services is one to enable in Services its normally a quick fix as well, the list above is not the whole story but I haven’t listed them all for clarity. It’s good idea not to get in to the “Master Browser” setting Reg Keys etc as not only its Registry work with all the dangers that has but, multiply the size of the Subnet by the number of possible permutations should anything go wrong, and, hence, a curious thing about the Master Browser election on a Network is that it tends to gravitate towards the older Machines such as Win7 and Win8x instead of having a “fair election” as to what’s booted up first. Strange eh?? such is the wacky world of “Windoze”

Reply | Quote

I have a Dell Latitude 5480 that was upgraded to 1803.  Didn’t notice any issues for two days after upgrading.  However, on the 3rd day after coming out of sleep, all I saw was a blank screen.  When I move my mouse, I would see the mouse pointer with the spinning ball.  I didn’t have this issue with the prior two days of having it come out of sleep.  My issue sounds like the Alienware laptops mentioned in the Computerworld article.

My fix was to revert the graphics driver (I have both the integrated Intel GPU and an Nvidia 930MX GPU).  The strange thing when I was checking the system is that Windows said that my temp files folder had been moved, but I set that back to what it was before…and everything seems to be okay with 1803…so far.

Reply | Quote

I am getting very slow performance when playing StarCraft Remastered

Reply | Quote

More 1803-fun… https://filezilla-project.org/ – MSW: Microsoft broke the ICopyHook interface in Windows 1803. Until Microsoft fixes the bug in Windows, drag & drop from FileZilla into Explorer will not work on Windows 1803.

Reply | Quote

Had some performance issues right after the update – one of the games was previously using around 10-15% of my CPU and GPU. This has increased to 90-100% usage for both after 1803.

I have clean installed NVIDIA drivers and Intel Graphic drivers and usage went back to normal.

Reply | Quote

My Western Digital Drives disappeared. One a WD 2TB Black and the other a WD 2TB Gold Enterprise drive. Occasionally if I left the computer on long enough they would reappear. I would have to go into Disk Management and import them. But later they would be gone again. Happened enough times to make the Gold drive corrupt. So I replaced it with a 1TB Green drive same issues. My motherboard has Debug codes on it it is hanging on A2 IDE Detect. My main drive is a Samsung 970 EVO 250GB NVME with common boot times of a minute sixteen seconds. I am now getting health warnings on my 2TB Black. And now when I reboot minutes go by and I end up manually shutting down. Upon restart it took a minute or two stuck on IDE Detect then finally the spinning dots of Windows Starting. I got tired of waiting layed down for 5-10 minutes and it still had not booted. I manually shut down opened my case unplugged the two SATA cords for my WD drives. Turned it back on and my boot time was within seconds. I am far from the only person having issues with 1803 and Western Digital. It has already killed one drive and started the process on a second one. I am buying a 4TB Toshiba as soon as I get paid.

Reply | Quote