Three known bugs in the latest build of Win10 version 1903

Topic

New Reply

Microsoft is supposed to be keeping us informed of bugs in Win10 versions, and you’d think they’d be particularly on-the-spot about following up on bu
[See the full post at: Three known bugs in the latest build of Win10 version 1903]

2 users thanked author for this post.

geekdom

Reply | Quote

Replies

I can successfully install/enable .NET 3.5 after v1903 CU KB4517211

i will test v1809 CU KB4516077 shortly

3 users thanked author for this post.

b, woody, geekdom

Reply | Quote

Interesting. I’m seeing reports that the installation fails with

Microsoft-Windows-NetFx3-OnDemand-Package: 0x800f0954

Reply | Quote

[abbodi86]

From what i read and search, the error is related to WSUS

there is this suggested workaround for 0x800F0954 error
https://social.technet.microsoft.com/Forums/en-US/win10itprosetup/thread/8bc98626-42de-4d7e-9fc1-2bc8658cc47b/#795e8763-3be0-492e-8a17-4d39c676bd20

and this describe it more clearly
https://p0w3rsh3ll.wordpress.com/2019/03/29/quick-tip-avoid-error-0x800f0954/

and this explain it on v1709
https://edulab.unitn.it/tecnici/fix-error-0x800f0954-installing-net-framework-3-5-or-any-optional-feature/

.NET 3.5 can be enabled as a feature, or installed as a package
both worked for me on v1903 after installing the latest CU

but i don’t use WSUS

i suggest who got the error to try to add /LimitAccess

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:G:\sources\sxs

where G: is the mounted ISO drive

• This reply was modified 5 years, 7 months ago by abbodi86.

Reply | Quote

0x800f0954 is a Windows Update error that says that it can’t connect to WSUS to get the requested update.  I saw this one recently when trying to install RSAT.

 

Reply | Quote

I was able to install .NET 3.5 on my PC running 1903 build 18362.295. I’m not sure why it is that build (its a brand new PC) but grateful it did not update.

Picasa Starter (which enables you to run Picasa on a photo collection on a NAS accessed by multiple PCs) needs .NET 3.5, which is important for me.

Chris
Win 10 Pro x64 Group A

Reply | Quote

I can’t after installing KB4517211 and I’m not behind wsus.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Well, did you checked the logs for details? you got the same error 0x800f0954?

Reply | Quote

No issue on 1809 either

1 user thanked author for this post.

woody

Reply | Quote

When there are problems, a reference and timely source is useful. Such a source answers two questions:

• Is it me or is it everybody?
• What can be done to fix the problems?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

woody wrote:

I know of three bugs

Six users with obscure issues out of 250 million using 1903 means about 0.0000024% had a problem with this week’s optional cumulative update (and recovered by uninstalling).

Is that seriously a meaningful measure of the “stability” of version 1903 for the vast majority?

Not to worry though: When 1909 arrives in a week or two it will become the big bad ogre to flee from and then 1903 will somehow magically become the one to hold onto at all costs.

3 users thanked author for this post.

zero2dash, bbearren, jayinalaska

Reply | Quote

Let’s see what happens.

Reply | Quote

I’m running Windows 10 Pro Version 1903 (OS Build 18362.387) and I have no effects from anything mentioned, with a single exception.

I use RDP a lot to administer my NAS and my laptop.  Whereas before, when I signed out of a system, I would see the “Signing out” screen for a bit before my desktop returned.  I no longer see that screen.  Instead I see a black screen for a bit before my desktop returns.  Other than that, RDP works just as reliably and stably as it always has.  Not an issue for me.

I have an hp all-in-one.  Cleaning up my desk last week, I intended to scan some stuff to .pdf and shred the hard copies.  The printer couldn’t find the PC.  I opened the printer UI on my PC, ran back through the “Scan to PC” wizard, and started scanning and shredding.  Not an issue for me.

The .NET Framework has never not been installed, but I went through the Windows Features add/remove, removed .NET and rebooted.  I then added .NET and rebooted.  .NET is back.  Not an issue for me.

The sky is not falling on everyone.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

5 users thanked author for this post.

Barry, abbodi86, zero2dash, jayinalaska, b

Reply | Quote

[IndyPilot80]

Regarding .NET 3.5 not installing.

I dont know if this will help anyone, but, I had to re-image a few computers due to still having start menu issues. .NET 3.5 would fail to install if those machines were in WSUS groups. Once I pulled them out, I was able to install .NET 3.5, then I put them back in.

EDIT: Just noticed someone posted “change the registry key UseWUServer to 0”.

• This reply was modified 5 years, 7 months ago by IndyPilot80.

Reply | Quote

[Fred]

b wrote:

Six users with obscure issues out of 250 million using 1903 means about 0.0000024% had a problem with this week’s optional cumulative update (and recovered by uninstalling). Is that seriously a meaningful measure of the “stability” of version 1903 for the vast majority?

Nice cifers… Put in a graph, some humble  dumble logarithms to the axes. Differentiate some values to the infinit… Voilà, outcome is practically zero [0]. No casualities and there is a stable version.

Keep them rolling out.

* _ ... _ *

• This reply was modified 5 years, 7 months ago by Fred.

Reply | Quote

I have another pack of complaints on Twitter. Here’s one that needs more info, but it’s an important one…

If multiple windows are open in maximized state & 1 app set to System/(Enhanced) DPI scaling, Fitt’s law of usability (shoving mouse in top right corner to close) is broken. It accidentally closes WRONG app’s window BEHIND it. Happens to the left corner or top window edge as well

Open Google Chrome maximized. Open Device Manager & maximize it. Now try to close Device Manager with mouse by shoving the pointer into the top right corner and left clicking instead of accurately positioning it over Close button. It accidentally closes Google Chrome

Can anybody out there confirm?

Reply | Quote

When all the bugs pan out. Is it simply, uninstall, that which you have installed. If MS will let you ?

Reply | Quote

Nope. Much easier than that.

Just follow the MS-DEFCON level. There’s no pressing need to install ANY of the September patches yet.

Reply | Quote

… and an interesting tweet from Tom Warren:

It’s amazing that Microsoft thinks Windows 10 May 2019 Update is ready for broad deployment when it’s not even ready for the company’s flagship laptop. Surface Book 2 is still blocked from installing 1903.

Reply | Quote

Only the top two models, not the other three.

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

… and an interesting tweet from Tom Warren:

The six replies from Surface Book 2 owners saying 1903 runs just fine for them are less interesting?

Reply | Quote

I thought everything was working fine after the latest update, but when I checked Event Viewer there were a lot of strange errors. Most of them were DCOM errors, but also driver issues. After I used the pc for an hour a log appeared in the Windows folder, stating that all my drivers were re-installed. I uninstalled KB4517211 and no more errors appeared.

1 user thanked author for this post.

woody

Reply | Quote

woody wrote:

Open Google Chrome maximized. Open Device Manager & maximize it. Now try to close Device Manager with mouse by shoving the pointer into the top right corner and left clicking instead of accurately positioning it over Close button. It accidentally closes Google Chrome Can anybody out there confirm?

I don’t (and won’t) use Google Chrome, but I opened Firefox maximized, opened Device Manager and maximized it.  The only way I can close Device Manager with the mouse is by clicking on the red X.  Clicking anywhere else in the right corner has no effect (as one might expect).

When I click the red X, Device Manager closes, and Firefox remains opened and maximized.  No unusual behavior.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren wrote:

I don’t (and won’t) use Google Chrome, but I opened Firefox maximized, opened Device Manager and maximized it.  The only way I can close Device Manager with the mouse is by clicking on the red X.  Clicking anywhere else in the right corner has no effect (as one might expect).

When I click the red X, Device Manager closes, and Firefox remains opened and maximized.  No unusual behavior.

I did exactly the same and I could reproduce the reported behavior. When the X has a red background, can you not continue off to the right so that the red background disappears again? That’s when a click closes the maximized window behind the maximized window you’re trying to close.

But it only seems to apply if the display is set to more than 100% scaling, and applies to all .msc admin tools like Computer Management, Device Manager, Disk Management, Task Scheduler, Event Viewer, etc., even Services.

However, I very much doubt whether this just surfaced with 1903; it’s probably been around forever. Only Fitts’ Law enthusiasts with their indiscriminate mouse slamming would notice it.

Reply | Quote

I tried to reproduce this bug with chromium and later manually setting chromium to System (enhanced), no dice. On a 4k monitor with a scaling factor of 1.5. I don’t have google’s Chrome build installed, so perhaps it’s different? Maybe the newer Chromium 79 developer build sets scaling itself?

I’m on a 1.5 scaling factor because my preferred scaling factor of 1.25 results in a bug in UWP platform apps that’s been around, unfixed, for a while. Perhaps this bug is another one that only occurs at certain scaling factors?

I’m not doubting the reporter, but perhaps the scenarios it occurs are more specific, or it’s even non-deterministic like the UWP bug I referenced above.

Reply | Quote

anonymous wrote:

I tried to reproduce this bug with chromium and later manually setting chromium to System (enhanced), no dice. On a 4k monitor with a scaling factor of 1.5. I don’t have google’s Chrome build installed, so perhaps it’s different? Maybe the newer Chromium 79 developer build sets scaling itself?

I don’t think Chrome specifically, or even the System (Enhanced) scaling, is a requirement to reproduce this apparent bugette (even though both were proposed by the originator).

From what I’ve now seen, the background app can be absolutely anything that you might want to have maximized on a high resolution display where you therefore have scaling above 100% (and Chrome is just a reasonable example of that).

It’s the foreground maximized app where the bugette becomes apparent; any .msc (Microsoft Management Console snap-in) like Device Manager. Highlighting the X to achieve red backgound, then mousing further right to lose the red background, followed by a left click; closes the background app, not the foreground app.

anonymous wrote:

I’m on a 1.5 scaling factor because my preferred scaling factor of 1.25 results in a bug in UWP platform apps that’s been around, unfixed, for a while. Perhaps this bug is another one that only occurs at certain scaling factors?

I tried at 150% on one screen and 125% on another; both seemed to cause the above effect with any .msc (which also includes Group Policy Editor).

anonymous wrote:

I’m not doubting the reporter, but perhaps the scenarios it occurs are more specific, or it’s even non-deterministic like the UWP bug I referenced above.

Using some search terms I hadn’t considered before, I think I just found some workarounds:

How can I make Microsoft Management Console high-DPI aware in Windows 8.1? (includes answers for Windows 10)

The crux of the problem seems to be that a Compatibility Tab with “Disable display scaling on high DPI settings” is hidden for system files, requiring registry tweaks for anyone who really cares.

But it’s clear that the issue has been around for a decade or so, has nothing explicitly to do with Windows 10 and certainly not version 1903; and I suspect that the report originator probably knew that.

Unless someone can test that this doesn’t happen on Windows 7, Windows 8 and versions 1803/1809, this should be struck off Woody’s list of minor quibbles with version 1903.

Reply | Quote

It’s the foreground maximized app where the bugette becomes apparent; any .msc (Microsoft Management Console snap-in) like Device Manager. Highlighting the X to achieve red backgound, then mousing further right to lose the red background, followed by a left click; closes the background app, not the foreground app.

I did try that, and still can’t reproduce. No matter how much farther I move the mouse up or to the right after highlighting the red X in device manager, it still remains highlighted and closes device manager after clicking the X. There is visibly a small amount of white space to the right of the highlighted X, but moving my mouse to the right does not result in unselecting the X or inadvertently closing the window below after clicking.

Maybe this has something to do with the visual effects settings? The only one I have enabled that’s relevant to windows is “Show window contents when dragging.” Maybe this only occurs if you have something else enabled? Maybe “animate controls and elements inside windows?”

Reply | Quote

Who knows? (Who cares!)

I could only get it not to happen when I set display scaling to 100%.

I was going to play around with dpiaware registry settings, but I don’t think it’s worth it.

I don’t see why anyone needs a Device Manager window that’s two feet wide (or any MMC tool).

Reply | Quote

woody wrote:

Nope. Much easier than that.

Just follow the MS-DEFCON level. There’s no pressing need to install ANY of the September patches yet.

Throughout my Windows experience (beginning with 3.11 WFW) I have always ignored expert advice at every level, preferring to discover the good or the bad on my own, with up-to-date drive images to save my bacon (used to use a Colorado Tape Drive for backup.  It was slooooooow).

I have, all by myself, pooched Windows literally 100’s of times by trying different things in different areas of the OS, restored my drive images and continued to tinker with lessons learned.

To the best of my recollection, no Windows Update has ever caused a serious issue for me, particularly Windows 10 Updates, to which I have been paying particularly close attention.  At present I have 5 installations of Windows 10 Pro in various configurations.

My daily driver desktop A side has Users sub-folders on a separate SSD using the location tab where available (the Microsoft supported solution).  I install programs and apps on another SSD.  I also use a utility called Application Mover to relocate any programs/apps that don’t offer an installation path option in the installation routine.  The only programs/apps still in C:\Program Files are those with Microsoft, Office or Windows as the first word in the folder name.

The B side is completely separated (the entire Users folder is on a separate SSD, etc.), and that installation is not supported by Microsoft, which has the distinct side effect of blocking Upgrades, but not Updates.  That involves a great deal of registry editing to accomplish, but I have utilities to facilitate that editing.

My DIY NAS runs Windows 10 Pro in a vanilla Microsoft supported installation, and also has four 3TB drives in a RAID 10 (or 1 + 0) array.

I also dual-boot my Dell Latitude E5420, one side using the Microsoft supported relocation of User sub-folders, the other side a vanilla Microsoft supported installation.

None of my installations have special folders or libraries.  I have completely ripped them out.  I have had no serious issues with any Windows 10 Update on any of those 5 installations.  Many updates kicked out my StartIsBack Start Menu, and I simply re-installed it after the upgrade and it continues to work flawlessly.  The last few have simply left StartIsBack intact and in use.

To sum up, I’m not an IT Pro, I only ride herd on my own home network, can be considered an experienced regular user, and in both standard and non-standard Windows 10 installations, I am a Seeker, I haven’t had any deal-breakers or serious issues whatsoever, and I continue to ignore experts, which is why I say,

The sky is not falling on everyone.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

Barry, Fred

Reply | Quote

[Fred]

hi Bbearren : a lot of “pro’s” may wish, or may have wished, to have you as a colleage!
Certainly the sky fell upon you, and gave you the blue hat of luck and patience!

Keep sharing please

* _ ... _ *

• This reply was modified 5 years, 7 months ago by Fred.
• This reply was modified 5 years, 7 months ago by Microfix.

2 users thanked author for this post.

RockE, woody

Reply | Quote

For what its worth I know my OfficeJet HP printer definitely has issues. Tried printing last night, printer downstairs so didn’t check on it til this morning and found printer screen just spooling and nothing printed. Did same printing on Mac and worked fine. So I know its not physically the printer at fault. But I have had printer issues off and on with Win 10 for awhile now.

Reply | Quote

woody wrote:

Microsoft is supposed to be keeping us informed of bugs in Win10 versions, and you’d think they’d be particularly on-the-spot about following up on bu
[See the full post at: Three known bugs in the latest build of Win10 version 1903]

Regarding one of the comments from 3 known bugs issue:

• The latest versions of Win10 1903 break some HP printers including. According to Tom Rogers on the Patchmanagement list:

“I installed the updated Sept 2019 Cumulative Update for Win10 x64 [1903] and it broke me printing to a network HP Color LaserJet Pro MFP M180NW… What happens in my case is the screen will flash, I hear the printer start, but then nothing. And then Windows closes any open windows. Almost like Windows Explorer restart. Job is not being held in the queue, printer is not offline (but HP software monitor says it is), this is a network printer I am testing on.”

I had a similar thing occurred for me during a previous Win10 1903 update.  I have a HP Officejet Pro 8610, but when Windows 10 was originally installed it installed “HP Color LaserJet Pro MFP M180NW” which worked just fine for originally, but stopped after an update.   My solution was to uninstall the incorrect printer driver and then reboot my PC and have it install a new printer driver – this time it installed HP Officejet Pro 8610 (printer/scanner) driver – now it works perfectly fine again.

Custom Build - Intel i5 9400 5 Core CPU & ASUS TUF Z390 Plus Motherboard
Edition Windows 10 Home
Version 22H2

Dell Laptop - Inspiron 15 11th Generation Intel(R) Core(TM) i5-1135G7 Processor
Edition Windows 11 Home
Version 23H2

1 user thanked author for this post.

woody

Reply | Quote

Posted this morning by Mayank Parmar on WindowsLatest:

On Microsoft community forum and Feedback Hub, some users are reporting problems with printers after applying Windows 10’s September 26 update on Microsoft community. Oddly enough, some users have also documented the printer issue on the Google support forum.

Reply | Quote

I’m afraid MS might not have been honest with us, or perhaps had no idea what they were talking about, when they blamed HP for the printer problems after their updates. On the last two major updates, I had serious problems getting my computer to communicate with my printer. The first time this occurred,  I spent over 5 hours on the phone with HP techs doing everything possible to communicate from computer to printer, to no avail. I finally was forced to do an in-place reinstall of the operating system to fix the problem. Unfortunately, it destroyed my system to the point that nothing was lost, but nothing worked. I had to reinstall every program. It would have been quicker to wipe my system and start from scratch.

The second time, on the last update, I got luckier. All four systems failed to communicate with the printer (all 4 were updated). Fortunately this time, I went through the HP diagnostics as I had the prior time. But this time that was able to correct all problems. Since I have not updated the drivers (there are no new updates for my printer and haven’t been for some time) and it now works, the problem appears to be on Microsoft’s end.

Reply | Quote