Cumulative updates June 2021

Thanks for all that information, fg2001. Yea for Backup & Restore! A Legacy install does not use Secure Boot which is another requirement for Win 11 (or maybe it's the same one). Interesting you could bypass those requirements. Does the computer also not have TPM 2.0? That's what I lack. What does TPM.msc (type into Search) say...?...

There's no mention of it in my BIOS. But I'm unsure I'd want Win 11 anyway (presuming a non-insider can clean install it) owing to the recommendation against it. But maybe I'll try it in a dual-boot to see for myself, if your reports are good. Is that how to bypass the requirements -- clean install it?

Hello PCR,

Well , I also have an older UEFI machine (Dell XPS 8700) that does not have TPM, so that does not meet the requirements either even if it is UEFI and has Secure Boot on.

As for Installing win 11 on Legacy BIOS you can find some workarounds on the web, just search "How to install Windows 11 on Legacy Bios machine".

Just doing a clean install using the Win 11 installation media will not work because it enforces the checks for the requirements.

One method that works is by replacing the install.wim or install.esd taken from windows 11 on a USB installation media of Windows 10 (21H1), then you can do the clean install from that and it will defeat the checks for the install requirements. All the files needed for windows 11 are in the install.wim in the Sources folder, everything else is just used for installing.

I'm sure MS can bypass the checks of the requirements for the windows insiders on development channels.

We'll just have to wait next week to see what MS will do.

As for fully supported machines, I have a Dell XPS 8930 Desktop and a Lenovo Yoga 920 which are both good to go for Windows 11. Still I'll keep the Backup of the current Public build so I can always go back to a stable system if anything goes wrong. Already tried and upgraded from 21H1 to win 11 with a win 11 ISO and it worked fine, then I restored my 21H1, I will be waiting for the official MS build, I don't really trust the leaked ones :-(

Thanks for all that information, fg2001. Yea for Backup & Restore! A Legacy install does not use Secure Boot which is another requirement for Win 11 (or maybe it's the same one). Interesting you could bypass those requirements. Does the computer also not have TPM 2.0? That's what I lack. What does TPM.msc (type into Search) say...?...

There's no mention of it in my BIOS. But I'm unsure I'd want Win 11 anyway (presuming a non-insider can clean install it) owing to the recommendation against it. But maybe I'll try it in a dual-boot to see for myself, if your reports are good. Is that how to bypass the requirements -- clean install it?

I'm glad I'm not alone using Windows Backup & Restore (B&R). Good to know it works for you too & for so long. IIRC, we discovered together in an old thread the computername folder could be renamed. Thanks for experiments with that. Until then, I was renaming the WindowsImageBackup folder itself which then had to be renamed back to use. MSFT did remove B&R from Win 8, but returned it in Win 8.1. I wonder whether it is in Win 11, but this computer won't ever know. It doesn't have TPM 2.0 which is a requirement. Too bad about that extra step for a clean Legacy install. I think I read Win 11 won't allow Legacy installs at all.

Hi PCR,

Already tried B&R With windows 11, still worked fine assuming they don't mess it up later.

As for Legacy Bios, is no longer officially supported by Win 11, but it still works using a workaround that bypasses the checks for the installation. I did a clean install of Win 11 on two Legacy Bios Machines and it seems to work fine.

According to this message on this current insider build 21390.1025 they still will allow to run Win 11 if you are already in the development channel at least until Win 11 goes GA, after that it will be the end of the game for old machines. 😒  

Will see what happens next week when we get an official Win 11 Build from MS.

The way I read the red message below, I think it should let me go on with Win 11 on this machine even if it does not meet the requirements.  

I'm glad I'm not alone using Windows Backup & Restore (B&R). Good to know it works for you too & for so long. IIRC, we discovered together in an old thread the computername folder could be renamed. Thanks for experiments with that. Until then, I was renaming the WindowsImageBackup folder itself which then had to be renamed back to use. MSFT did remove B&R from Win 8, but returned it in Win 8.1. I wonder whether it is in Win 11, but this computer won't ever know. It doesn't have TPM 2.0 which is a requirement. Too bad about that extra step for a clean Legacy install. I think I read Win 11 won't allow Legacy installs at all.

It took me a year/so too to make my first system image backup. Some do say Windows Backup & Restore is unreliable. But it always makes images of my 40 GB/so used space in about 15 minutes, & that one time I needed to restore one was just as quick. Also, it fills the Previous Versions tab of a file/folders' Properties so that the image not even need be mounted to recover a stray file. But I'm sure your 3rd-party app can also retrieve individual files & is quicker & makes more compact images. Wow, I don't understand it took hours for you (& then a crash) unless you had it also image your separate data drive & that one is enormous. It does sound as if you are better off with AOMEI. I must admit, at every new Windows version (not OS Build) I also make a second image using Seagate's free DiscWizard. I've heard good things about Apple's Time Machine before. Very nice.

Hi PCR,

I've been using Windows Image Backup for years and it still works fine, I use it every week after an update with a new insider build and I can restore a working system very easily if there is any issue.

My system  in every machine is on SSD which is used only for the Windows system and the installed programs, all my data is on a separate internal HDD, which I can also use to save Windows Image Backup if I don't want to connect an external drive.

MS screwed up the recent default layout of the disks for Legacy Bios when they decided to assign only 50MB to the System Reserved Partition on a clean windows install, that prevents the backup from working because it needs 50MB of free space to do the shadow image.

That problem can be easily eliminated by preformatting the partitions correctly to avoid that specific bug.

With the UEFI layout everything still works correctly with the default partitions created by a clean install.

I also use Macrium if I want to clone the system disk, but usually I'm quite happy with the MS Image Backup.

I just hope they don't drop it or deprecate it as they often keep saying.