Reverted
I tried it, my storage started acting all Boris-like, fluffy, incoherent, mistaken, catastrophic.
So I reverted, all is now Starmer.
The Windows 10 2004 rollout is moving a little quicker than the last major update to Microsoft's OS. Figures from Ad Duplex show the May 2020 Update hitting 7 per cent of the 150,000 Windows 10 PCs surveyed by the organisation to the end of June. The growth has been mainly at the expense of the previous three incarnations. …
So far, only one PC has been offered and accepted the new version. I cannot say it has anything to offer me. Another machine with an almost identical build is still waiting for the offer. Two others are pending possibly for their own good reasons. So far I have to say it is not worth the hype. A bit like Starmer and lawyers in general, loads of ballyhoo but not a lot of point.
Quote: "...image with all updates included like Linux community."
Huh? Is this a specific distro?
I've installed a few Linux installs over the last few months, desktop and server, VMs and real hardware, different distros, and always from a freshly downloaded ISO. The ISO only usually changes if the release number changes, and they always need an update/upgrade once installed [*]. i.e. the ISO for Ubuntu 20.04 is still the same now, as it was months back, so needs even more downloads to bring up to date.
* Not a complaint, just an observation, I expect to have to update any fresh install, and at least with Linux, it's usually quick and painless (especially server editions).
I updated, and then deleted the Windows.old folder.
I didn't use the builtin Windows Tool for that, instead, I just took ownership of the directory contents and changed the ACLs and did an RD /S
Don't try this!
Somehow inside Windows.old are a bunch of links to live files on your system. In my case, all my local mysql databases, which were all wiped.
I then factory reset the machine and installed Windows 2004 from scratch, so far I have not had any issues.
Fresh install also worked for me, although I've only done this successfully on a single test box so far (real hardware).
The one test VM I updated to 2004, (from 1909), has been glitchy, odd stability issues, video flickers, NAS drive dropouts etc. Could be partly an incompatibility with Virtual Box, lots of people complaining about the video issue. A fresh install of 2004 in a VM still had video issues (very very slow), but other things like NAS drives seem to work okay, so far anyway.
Won't be letting 2004 anywhere near any of my 'real' PCs any time soon.
Several of us at work have upgraded early for WSL2. Most won't get it for a few months. Some have had trouble actually getting it to start the upgrade in the first place but I haven't heard of any problems once upgraded. I've already switched my main dev environment from VirtualBox to WSL2. There's a couple of rough edges but the performance alone makes it worthwhile.
WSL2 is the one thing I'd really like 2004 for, but my main PC current states that I can't update from 1909 to 2004 [*] atm, and other test updates on other boxes, haven't exactly got smoothly! So I'm going to wait a while.
* It just says the update is not ready for my device yet, they'll let me know once it is!
Depends...
Upgraded a load of customers in Feb~Apr to 1909 in readiness for lockdown.
Currently, 2004 is in the optional list on some of the machines where it can stay until it becomes easier to physically access the machines currently distributed to people's homes and they have a (small) stock of upgraded machines that can be swapped.
However, like you, all new machines will be 2004.
I don't remember quite how but I tamed my New Folder page quite quickly, starting with the Focused option.
It now has a very clean look, showing only the Microsoft icon+name, the Search box, and my eight favourites. No extensions.
Running Windows 10 Pro, 20H2, build 19042.330.
We should all therefore take a moment to pay tribute to that brave 7 per cent, willing to set sail into the uncertain waters of Windows 10 2004 and click Check for updates.
WILLING to set sail .................
my PC effectively TOLD me it was waiting to update, started, it hung, and stayed there for hours, shut down, restarted, PC back to as was, all good, two days later, the PC again, told me it was waiting to update, started, and this time it went through
all good so far, but TBH, I am not a major user at home on Windows, so maybe I haven't found the trip wires yet LOL
I had the message on my laptop, desktop and tablet machines that the update was not ready for me yet, for a so long, I got bored and added my laptop to the Insider Ring, I now have my very old Dell Studio 17 Dual Core machine running 20H2 19042.330, seems a bit nippier than previously, I think if I replaced the hard drive with an SSD the speed increase would be very noticeable.
Am I odd in that before shutting down any of my PCs, I generally go and "Check for Updates" and let it install what it needs, probably cursed this now, but I've never had any major issues, I think once, the camera stopped working on the Surface tablet, but it was back up and running again within a week.
My main Windows desktop is a hand build and has Win 10 Pro, Win 10 Edu, Win Server 2012 R2, and Ubuntu 18.04 in different volumes. The Pro and Edu volumes both got 2004, no problems, no wait. (Note that that’s different _volumes_, as in different physical drives, currently a 1 TB HDD each for Win 10 Pro and Edu, a 2 TB HDD for 2012 R2, and a 3 TB for Ubuntu.) This machine started with Win 7 and Server 2008 R2, so it’s not exactly new. I have the Server install as an emergency system if my main server goes TITSUP, so that volume gets started mostly for updates and to make sure it still runs.
I'm using a corporate [*] laptop, and we are still on 1809 (Enterprise), and all updates are managed by the company, so can't even force an update to 1909, let alone 2004.
Corp has 50,000+ employees worldwide, so that's a small amount still on 1809 globally, but still quite a few.
My work laptop is still on 1709, although the company is preparing to upgrade to 1909 in the next month or so. To be honest, I don't mind. There are pretty much zero benefits I can think of to my daily work from a newer build, and instead the risk of my system borking during the upgrade and hence preventing me from getting anything done is of bigger concern to me.
My wsus server automatically approved and published 2004 for all computers in my org. Earlier Win10 feature updates required manual approval and license agreement before roll out.
This behaviour will make a big impact on achieving 7%!
Yes, we do have some problems with it.
it blew away the linux dual boot installation by adding a 450 MB WinRE hidden partition out of the space used by / on a sandpit box. Same on HP laptop of little use.
No warning, just no linux installation. Seems to be designed to enforce EUFI and preventing dual boot on traditional BIOS dual boot. As for Windows, the little I use it, nothing to make it desirable. Still have to find 3 drivers for Nvidia and a couple of other chips. All Win 10 Pro versions.
Update blew away the linux dual boot installation by adding a 450 MB WinRE hidden partition out of the space used by / on a sandpit box. Same on HP laptop of little use.
No warning, just no linux installation. Seems to be designed to enforce EUFI and preventing dual boot on traditional BIOS dual boot. As for Windows, the little I use it, nothing to make it desirable. Still have to find 3 drivers for Nvidia and a couple of other chips. All Win 10 Pro versions.
I tried installing it a few days after it released, it totally messed up my desktop, explorer would not run, no access to any program, errors everywhere almost like the windows folder was missing. I managed to use an windows 10 install USB to access the update rollback and bingo everything was back to normal. I just hope it is fixed when they force the install on me.....
On the things that matter, if I use Remote desktop, I had a ton of issues from Windows 10 to Windows Server 2019 (never had an issue with 2016 but a hardware failure led to me upgrading to 2019 for faster Windows Updates application times). These issues have disappeared with 2004. I got rid of the crummy Dell TB3 docks so I also avoided that issue.
So at least for my use cases, it is an improvement on an abysmal product :)