Windows 10 May update.

[UsandThem]

Well, the update is available again on my laptop after being pulled on May 30th. I'm still going to wait for a few more weeks to let them iron out more bugs before taking the plunge.

10 years ago I would have installed it on day 1, now not so much.

 

[JackMDS]

Installed on few computers and every thing went well.

Then, the last 2 computers Trashed the existing 1809.

These two had only 12GB space free. No warn came up alerting to insufficient space.

Putting a 32 GB clean USB solved the problem.

So... now I am using the USB on each Upgrade No matter what the internal Drive empty space.

 

[VirtualLarry]

So... now I am using the USB on each Upgrade No matter what the internal Drive empty space.

How are you doing that, Jack? The version of 1903 that was downloaded when I made my USB install stick a few days ago, when I went to upgrade a PC to 1903, it popped up a warning about hardware incompatibility, because there was external USB storage detected, and installation wouldn't continue. So basically, the version of 1903 that is now available (?), WILL NOT let you upgrade using a USB stick, run from within an existing installation of Win10. (Basically, the source USB stick with the installer files is detected as external USB storage, and blocks the install. A fresh install booting from the USB stick is still possible, however.)

 

[RLGL]

I had no issues upgrading an old Dell with a USB stick.

 

[JackMDS]

I did not do any clean Install all the 10 Upgrades are on functional 1809.

Computer are from an old Dell 530s2 (E8400) to Kaby Lake i7.

USB install generated as ISO from MS Media and installed on 32GB USB3 with Rufus.

P.S. because of old professional software used on this computers they are configured as MBR.

 

[mv2devnull]

Well, the update is available again on my laptop after being pulled on May 30th.

I did check yesterday and for the first time ever the WU did show 1903. Had no time to run then.
Now, 1903 vanished.

The 1809 has never been offered to me; still on 1803.

 

[VirtualLarry]

I did check yesterday and for the first time ever the WU did show 1903. Had no time to run then.
Now, 1903 vanished.

That happened to a friend of mine today. He was doing updates, and checking his activation, and it showed that 1903 was available one minute, and gone the next time he clicked "Update".

 

[bbhaag]

Just got the notification today and I'm in the process of upgrading from 1809 to 1903.

 

[pcslookout]

I did a fresh install of Windows 10 Build 1903!

 

[UsandThem]

I decided to try the update on my laptop since I just use it mainly for browsing, and all went very smooth (and much quicker than I thought it would be). I did the update through Windows Update, and not through a Windows ISO on a USB drive like so many here have done. I did notice it created a "Windows.old" of the previous install build which was a little over 27 GB in size. I'll delete that eventually once I am sure there's no need to roll back to the prior version.

After figuring out how to get my task bar and start menu back to being dark (without using the dark theme), everything is so far working as it should.

 

[VirtualLarry]

Don't just delete Windows.old manually. Use Disk Cleanup. (Ask me how I know.... those "special folders", the ones with a period and a GUID appended, if you manually delete them in Explorer, they do BAD THINGS to your EXISTING INSTALLATION.) Trust me. Do it using the "official way". Or use a Linux boot disk, that won't follow the "special folder links".

Edit: As for performance problems, I do seem to notice my Bay Trail Atom dual-core N2830 laptop (with SATA 2.5" SSD installed), seems to be ever-so-slightly but noticeably slower, in 1903. I'll get used to it.

 

[UsandThem]

Don't just delete Windows.old manually. Use Disk Cleanup. (Ask me how I know.... those "special folders", the ones with a period and a GUID appended, if you manually delete them in Explorer, they do BAD THINGS to your EXISTING INSTALLATION.) Trust me. Do it using the "official way". Or use a Linux boot disk, that won't follow the "special folder links".

Yeah, that's how I always delete them (through Windows disk cleanup).

 

[VirtualLarry]

Perhaps ironically, I recently upgraded my main desktop PC running Win10 1809 Pro, to 1903. I then had some issues with it, so I had to do System Restore, though not to before the upgrade. Now, when I went to Disk Cleanup, System Files, I don't see "Previous Windows Version" under the cleanup items. And Windows.old is still on my drive. Guess it's time for a Linux boot USB, when I get the chance.

 

[deustroop]

No, the option to delete .old in Disk Cleanup is not available for some short period post the upgrade to keep it available to revert to the previous version.

 

[VirtualLarry]

No, the option to delete .old in Disk Cleanup is not available for some short period post the upgrade to keep it available to revert to the previous version.

Hmm, can't say that I've ever seen it not show up immediately after upgrading Windows, but show up "later". Usually when I upgrade Windows 10 to a new version, in-place (thus generating a Windows.old directory), I usually test it out for a few hours, then delete the Windows.old the same day.

I'll keep an eye out to see if it shows up under Disk Cleanup, System Files, Old Windows Version, but I doubt that it's going to show up. I think that I borked it somehow.

 

[WilliamM2]

Hmm, can't say that I've ever seen it not show up immediately after upgrading Windows, but show up "later". Usually when I upgrade Windows 10 to a new version, in-place (thus generating a Windows.old directory), I usually test it out for a few hours, then delete the Windows.old the same day.

I'll keep an eye out to see if it shows up under Disk Cleanup, System Files, Old Windows Version, but I doubt that it's going to show up. I think that I borked it somehow.

It's always appeared immediately for me too. I always write an image before updating, and run disk cleanup right after the update. If I need to go back, I'll use the image. 1903 was no different.

 

[deustroop]

Ok I must be drinking too much coffee.

 

[Ketchup]

Haven't had any issues upgrading several VMs and real machines at this point. One oddity was a clean install VM, when I started typing out "calc" in the search box, it said I needed to get one from the app store. Really Microsoft? The calculator? My past 5 phones (pprobably more) have come with calc for Pete's sake! I guess they can now this is the first version of Windows to ever not come with a calc (well, maybe I wouldn't advertise that).

 

[deustroop]

Is this what you mean ?

I got calc in ver 1903

 

[UsandThem]

Maybe it's because you are running it in a VM? Otherwise, I'm not sure why it would be prompting you to download it.

The calculator has come standard in all my Window 10 PCs (seven total) without having to download it from the Microsoft Store. My PCs are a mix of 1903 Windows builds, and some running the previous version

 

[Ketchup]

Should have, but no. Maybe my fresh install (which was a full reset started from withinn an existing 1903 upgrade) went a little wonky.

 

[Ketchup]

Maybe it's because you are running it in a VM? Otherwise, I'm not sure why it would be prompting you to download it.

The calculator has come standard in all my Window 10 PCs (seven total) without having to download it from the Microsoft Store. My PCs are a mix of 1903 Windows builds, and some running the previous version

Yeah. It's an odd one. I have done re-installs on VMs with 10 plenty of times and never saw anything like it.

 

[deustroop]

Try to create a new user profile with admin privileges. On that profile, try to access Calculator . If the error message is gone, the current user profile that you have is corrupted . You may have to go to the Microsoft Store and reinstall Calculator in order to resolve the issue. Not sure how it got corrupted/uninstalled.

 

[Ketchup]

I already went to the store and installed a calc app, so it's fine. If I have time to mess with it, I will try the same procedure on my backup copy and see if it does the same.

 

[Ketchup]

Here is what I am talking about. Here is another VM I did a reset on, off the same image:

https://imgur.com/wvvqs0Y