Windows 1903 - just reverted back to 1809

[Valantar]

8.1 was perfectly fine for me, ever had any issues with it. That's why I refused to update to W10 up until late point when they've started to disable the "disability" free upgrade path.

I liked the 8.1 UI on touch-enabled convertibles (8 was okay there too, but less flexible), but could never stomach it's "take it or leave it" approach to the start menu on the desktop. And I refuse to use a third-party app to replace the start menu - that's just too dumb. Having that grid of "touch-friendly" tiles spread across a 27" monitor made me dizzy. I love the W10 start menu, though. Far better than the W7 one. Other than that, my only long-term experience with the W8.x series was my partner's extremely buggy Lenovo Yoga, which we finally got refunded after three years, two motherboard swaps (both had faulty RAM, which baffles me to this day), one display swap, and one more "unrelated" service centre visit (they apparently didn't want to tell us what they fixed). That it came with an OEM 840 Evo-alike that never got a firmware update to alleviate performance degradation was just the icing on that laptop-turd cake. But while it worked, as I said, I liked the OS in that form factor. I also like W10 on my convertible Latitude 7390 And W10 pen support is amazing (in MS apps, that is - everyone else is way, way behind on that front). I started using W10 Insider Previews before launch on my old laptop (an old ThinkPad X201) and the positive experience from that led me to upgrade from W7 to W10 on my desktop almost as soon as it launched. That install even survived upgrading that PC from an ages-old Core2Quad platform to my current Ryzen, which to me about sums up the flexibility and stability of W10 in my experience. Switching the same install between platforms 10 years apart from different vendors, with only the GPU and storage carried over? No problem, just let me update some drivers at first boot. (I obviously still did a clean install soon afterwards, but it worked!)

 

[Papahyooie]

Side note, just for everyone's information... If you clean install 1903, you can't uninstall the "App installer" program that installs crapware from the Microsoft store...

Haven't delved further into:
1. Whether the update installs it on a machine that previously had it uninstalled
2. Whether there are any other ways to effectively neuter it.

All I know is, I clean installed 1903 on a machine, and the App Installer program is now locked as a system app (option to uninstall is not there/gray'd out) like many of the other pieces of bloatware.

 

[P4-630]

I'll just wait, at least till end May,

Current status:
Windows 10, version 1903 is available by manually selecting “Check for updates” via Windows Update. (Note We are slowly throttling up this availability while we carefully monitor data and feedback.) The recommended servicing status is Semi-Annual Channel.

Windows 10, version 1903 and Windows Server, version 1903

View announcements and review known issues and fixes for Windows 10 version 1903 and Windows Server 1903

docs.microsoft.com

About the known issues as in the link above: Microsoft is working on a resolution and estimate a solution will be available in late May.

Also if you do check for updates manually:
Clicking “Check for Updates” Makes You a Tester

Don't Click "Check for Updates" Unless You Want Unstable Windows 10 Updates

As Microsoft revealed, only people who clicked "Check for Updates" got bitten by Windows 10's file deletion bug.

www.howtogeek.com

 

[FYFI13]

Side note, just for everyone's information... If you clean install 1903, you can't uninstall the "App installer" program that installs crapware from the Microsoft store...

Haven't delved further into:
1. Whether the update installs it on a machine that previously had it uninstalled
2. Whether there are any other ways to effectively neuter it.

All I know is, I clean installed 1903 on a machine, and the App Installer program is now locked as a system app (option to uninstall is not there/gray'd out) like many of the other pieces of bloatware.

CCleaner was able to uninstall it for me, just like any other UWP app, including MS Store itself.

 

[rtwjunkie]

Also if you do check for updates manually:
Clicking “Check for Updates” Makes You a Tester

Don't Click "Check for Updates" Unless You Want Unstable Windows 10 Updates

As Microsoft revealed, only people who clicked "Check for Updates" got bitten by Windows 10's file deletion bug.

www.howtogeek.com

Oh hell no! Why do they keep relegating anyone but the basic user to the trash heap?

 

[erpguy53]

Also if you do check for updates manually:
Clicking “Check for Updates” Makes You a Tester

Don't Click "Check for Updates" Unless You Want Unstable Windows 10 Updates

As Microsoft revealed, only people who clicked "Check for Updates" got bitten by Windows 10's file deletion bug.

www.howtogeek.com

that howtogeek article has not been updated since Oct 2018

 

[P4-630]

that howtogeek article has not been updated since Oct 2018

I just can't find it anymore on TPU, there was a news post about it a while ago here as well.

 

[AltCapwn]

I guess I'm the lucky guy who never had issue with any Windows 10 release.

 

[Laurijan]

Since wednesday i have the new build installed and the rig feels more sluggish now and boot slower from time to time. today my rig had its first hangup. I bet its all becasue of this update.

 

[theFOoL]

You people are on crack. On my 775 Build and even my Server the Box Build i3 3150 I see no changes in boot and both are msata+case Sata SSDs

 

[Ware]

taskbar color is stupidly flat grey and there is nothing i could do to make it black...

what a bunch of nagging lazy folks at microsoft

This place needs a special section for stuff like this.
I think a quote applies here -
"Better to Remain Silent and Be Thought a Fool than to Speak and Remove All Doubt"

 

[ExV6k]

1. My custom lock screen pic is blurred...WTF?

2. Installing AMD graphics drivers causes my entire screen to change to a solid color(so far either red or magenta) until I restart.

3. They changed the location of icon files. I had to figure out where they went(C:\Windows\SystemResources\imageres.dll.mun), so I could do my "make the blue and yellow UAC shields disappear" trick. Thankfully I was able to perform that without issues.

Other than that...oh wait...one more...

4. I can't stand the way they changed the Downloads folder to show separate groups. Hopefully there's an easy fix for that. If there is, and you know of it, I'm all ears.

Other than that...it's fine.

There is a fix indeed.. Except I encountered a bug when applying it.. But there's a workaround for that too!
Basically, all you have to do is right click, select "Group By" and hit "None". Now this should in theory do the trick but for some reason, it doesn't save your setting and all it takes for it to reset is refreshing the folder. If you want to force it to save, you'll have to Group By None again and then sort it by anything you want (Right click, "Sort By" --> Name / Type or whatever. You have to change the Sort By setting at least once after Grouping to force the explorer to save your choice).

 

[Zyll Goliat]

Well...I kinda liked this 1903 Win build....After I shutdown all useless services and performance"eaters" everything working well&smooth.....also honestly I prefered download folder to be like this is much more distinct after you get used to it....and yeah I kept darker taskbar,for me it's just more stylish.....

 

[Papahyooie]

CCleaner was able to uninstall it for me, just like any other UWP app, including MS Store itself.

Really? I haven't used CCLeaner in years (I just refresh/reinstall if things get too hairy). I had no idea it could do that. Thank you!

 

[Static~Charge]

I just upgraded my test machine from 1809 Pro to 1903 Pro. I was unable to do the upgrade from a flash drive. The installer complained that it didn't have drivers for some of the PC's hardware. Seriously? It's a B75 chipset with a 3rd generation Core i5 processor -- not exactly state-of-the-art, but not ancient, either. And Microsoft's description of the problem was b.s.; my test machine doesn't have any of the hardware that they listed ("an external USB device, SD memory card, or UFS card attached"). Was the installer complaining about the flash drive that contained Windows 10 v1903? If so, the error message is even more asinine: if I'm installing off a flash drive (the usual method nowadays), why complain about an external USB device?!

As an alternate approach, I ran the Windows Upgrade Assistant. This program upgraded my test machine to 1903 without a fuss.

The only usual thing that I spotted so far: I can't open the Windows 10 Apps menu (Start > Settings > Apps). When I click on Apps, the window opens for a second and then disappears. I ran “sfc /scannow” to check for corrupted system files; nothing found. All of the other items on the Settings menu open just fine. I'm debating whether to look for fixes or just roll back to 1809.

 

[Deleted member 171912]

How?

- First, install latest updates for OS, applications and drivers.
- Then download ISO file (win10_1903_english_x64.iso), don't use or wait for Windows Update.
- Log on, eject external disks, mount ISO file, setup.exe, accept download updates during setup (setup updates), restart.

And you will have new OS build will rollback option. Then, after some days, delete old OS files and backup files with Disk Cleanup tool.

30 minutes and no problems, like always. Build 1903 is already on 3 different computers. Enjoy.

 

[P4-630]

that howtogeek article has not been updated since Oct 2018

January 15, 2019: https://www.auslogics.com/en/articles/do-i-need-manually-check-for-win10-updates/
"Keep in mind that when you click the ‘Check for updates’ button,
you will install Windows updates that are still riddled with undiscovered issues.
As such, if you are not an advanced Windows 10 user, we recommend waiting for Microsoft to offer the updates to your system.
This is the only time wherein you can rest easy knowing that the system is completely stable."


December 14, 2018: https://www.ghacks.net/2018/12/14/here-is-another-reason-to-avoid-check-for-updates-in-windows-10/
"If you activate "check for updates", pre-release updates may be installed on the device.
Microsoft displays no warning prompt or notification to users that they may install pre-release updates when they use the "check for updates" button to run a manual check for updates. "

 

[TheoneandonlyMrK]

Im on a Ryzen main rig, i noticed i got back a smidge of performance that 1809 seamed to miss out on , no issues though i did get a BSD the first time i tried to update while fully overclocked.
resetting to defaults and rebooting ,then updating then worked fine ,and has since, it overclocked fine once done.

 

[Regeneration]

Can't access monitor settings (refresh rate) from within Windows (rundll error) on a clean installation of 1903.

 

[biffzinker]

Can't access monitor settings (refresh rate) from within Windows (rundll error) on a clean installation of 1903.

Haven't ran into that myself although I upgraded instead of a clean install.

If I have time later I'll try a clean install on a unused ssd I left plugged in.

 

[Metroid]

Haven't ran into that myself although I upgraded instead of a clean install.

If I have time later I'll try a clean install on a unused ssd I left plugged in.

I always do a clean install, too many issues with permissions if I choose to upgrade. I'm planning to upgrade to 1903 when I get the ryzen 3900x. I'm using 1709 and so far is very stable, no issues if you do a clean install. I tried 1803 while ago and was disappointed, many applications had issues, reverted to a clean 1709 install. It was a mess.

 

[biffzinker]

I always do a clean install, too many issues with permissions if I choose to upgrade. I'm planning to upgrade to 1903 when I get the ryzen 3900x. I'm using 1709 and so far is very stable, no issues if you do a clean install. I tried 1803 while ago and was disappointed, many applications had issues, reverted to a clean 1709 install. It was a mess.

Usually I do a clean install just to play it safe, and clean out cruft that's built up. The couple of times I've upgraded went without any trouble.

 

[Vayra86]

You're describing LTSC, more or less, but yeah, I agree. It would be awesome if regular users could get that without having to do a lot of tweaking.

Two new versions each year is too much tho. One would be enough, and would it would hopefully have a bit fewer bugs at launch.

This is Agile development man, its all the rage these days. You release a lot, and hope it sticks. When it doesn't, you release some more. Amazing 'time to market', much profit

 

[Static~Charge]

And Microsoft's description of the problem was b.s.; my test machine doesn't have any of the hardware that they listed ("an external USB device, SD memory card, or UFS card attached"). Was the installer complaining about the flash drive that contained Windows 10 v1903? If so, the error message is even more asinine: if I'm installing off a flash drive (the usual method nowadays), why complain about an external USB device?!

I think that I may have found the source of the error message when I tried to upgrade my test PC to Windows 10 v1903:

Fixes for Windows 10 arrive (for Insiders, soz) and covers are pulled from Edge for macOS

More Mac tickling with Defender ATP and Visual Studio gets a point one

www.theregister.co.uk

Windows 10 1903 is here and there's already a mighty big patch for it

There was no rest for the wicked (as the Windows team is occasionally referred to by its customers) as a raft of fixes arrived for the newly GA'ed May 2019 Update in the form of build 18362.145.

And by goodness, the gang has been busy. Among the lucky 13 changes is one to fix the infamous external storage borkage, which led to a reassignment of the drive letter during installation and an unhelpful "This PC can't be upgraded to Windows 10" error message.

Now all I need is an updated installer that incorporates this fix.

 

[Deleted member 24505]

I've been on 1903 since 09/04/19 , and it is very stable for me, even though it was probably a "test" build. I have had absolutely zero problems or crashes. I can't really understand anyone's problem with it. My build no. is 18362.116