Updating From 10 to 11 Secure Boot & TPM Question

NavyLCDR said:

Code:

C:\windows\system32>diskpart

Microsoft DiskPart version 10.0.22000.1

Copyright (C) Microsoft Corporation.
On computer: RAIDER

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          953 GB      0 B        *
  Disk 1    Online          465 GB      0 B        *
  Disk 3    Online          127 GB      0 B

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     F   ESD-ISO      UDF    DVD-ROM     4327 MB  Healthy
  Volume 1     D   Data         NTFS   Partition    945 GB  Healthy
  Volume 2     R   RECOVERY     FAT32  Partition   8191 MB  Healthy
  Volume 3     C   Windows      NTFS   Partition    443 GB  Healthy    Boot
  Volume 4                      FAT32  Partition    100 MB  Healthy    System
  Volume 5         WinRE tools  NTFS   Partition    980 MB  Healthy    Hidden
  Volume 6         BIOS_RVY     NTFS   Partition     21 GB  Healthy    Hidden
  Volume 7     E                NTFS   Partition    126 GB  Healthy

DISKPART>

Disk 3 is where I want to install Windows 11 to, MBR booting in legacy BIOS mode. Drive F: would be my standard USB flash drive created with Microsoft's Media Creation Tool. To open the command prompt press Shift + F10 after booting the computer from the USB flash drive.

Code:

DISKPART> select disk 3

Disk 3 is now the selected disk.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> create part pri size=100

DiskPart succeeded in creating the specified partition.

DISKPART> active

DiskPart marked the current partition as active.

DISKPART> format fs=ntfs quick label="System Reserved"

  100 percent completed

DiskPart successfully formatted the volume.

DISKPART> assign letter=s

DiskPart successfully assigned the drive letter or mount point.

DISKPART> create part pri

DiskPart succeeded in creating the specified partition.

DISKPART> format fs=ntfs quick label="Win11"

  100 percent completed

DiskPart successfully formatted the volume.

DISKPART> assign letter=t

DiskPart successfully assigned the drive letter or mount point.

DISKPART> exit

Leaving DiskPart...

C:\windows\system32>f:

F:\>cd sources

F:\sources>dism /get-wiminfo /wimfile:install.esd

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Details for image : install.esd

Index : 1
Name : Windows 11 Home
Description : Windows 11 Home
Size : 15,918,540,541 bytes

Index : 2
Name : Windows 11 Home N
Description : Windows 11 Home N
Size : 15,229,765,223 bytes

Index : 3
Name : Windows 11 Home Single Language
Description : Windows 11 Home Single Language
Size : 15,921,439,394 bytes

Index : 4
Name : Windows 11 Education
Description : Windows 11 Education
Size : 16,201,186,274 bytes

Index : 5
Name : Windows 11 Education N
Description : Windows 11 Education N
Size : 15,500,722,223 bytes

Index : 6
Name : Windows 11 Pro
Description : Windows 11 Pro
Size : 16,198,033,078 bytes

Index : 7
Name : Windows 11 Pro N
Description : Windows 11 Pro N
Size : 15,515,196,102 bytes

The operation completed successfully.

F:\sources>dism /apply-image /imagefile:install.esd /index:6 /applydir:T:\

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Applying image
[==========================100.0%==========================]
The operation completed successfully.

F:\sources>bcdboot T:\Windows /s S: /f BIOS
Boot files successfully created.

F:\sources>

Reboot the computer into the newly installed Windows 11 on the hard drive (or SSD). Took me less than 2 minutes to type the commands. Waiting for the image to apply is the longest part of the procedure. Only minor changes are required in the commands to install to GPT disk and boot in UEFI mode.

Click to expand...

I would not classify using commands in diskpart and DISM to being simple and easy. Most people do not want to have to type in commands. When I have to resort to doing it, I'm annoyed. I feel like I'm back 30 years in the past using DOS or even worse, CP/M.

Or--even worse than that---Linux

fmw said:

Well I tried to do what you say and failed. Since I am pretty knowledgeable about computers and once owned and operated a computer company, that makes it something other than trivial for me. I've read several posts explaining the process and not one worked for me. What worked for me was setting up 11 on a supported system and cloning drives from it. I can chalk it up to age, I suppose. I don't do things as well as I did as a young man.

Click to expand...

Try any of these methods. They all amount to the same thing in the end, just different approaches to the same thing:

***************************************************************************
* How to Bypass Windows 11 Installation Requirements with a Clean Install *
***************************************************************************

All of these methods basically set Windows registry setting in Win PE. THEY WILL NOT affect the final installed Windows at all, only the temporary Win PE loaded in memory during setup.

****************************************************
* Method 1 - Using an Autounattend.xml Answer File *
****************************************************

Note: The answer file does NOTHING except set the registry settings that bypass Win 11 requirements. It does not automate installation.


Create a new answer file or modify an existing answer file with the following entries:

Add the component Microsoft Windows Setup\RunSynchronos\RunSynchronousCommand to Pass 1 windowsPE

Set the following values:

Order: 1
Path: reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f

Repeat the above steps 4 more time (for a total of 5 "RunSynchronousCommand" entries) with the following entries:

Order: 2
Path: reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f

Order: 3
Path: reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f

Order: 4
Path: reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f

Order: 5
Path: reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f


**************************************************
* Manually Modify the Registry for Windows Setup *
**************************************************

At the first static screen where Windows setup requests information from you during setup, press SHIFT + F10 to open a command prompt.

Type regedit and hit ENTER. Add the following entries:

HKLM\System\Setup\LabConfig BypassTPMCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassSecureBootCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassRAMCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassStorageCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassCPUCheck reg_dword 0x00000001

Close Registry Editor and the command prompt. Continue installation normally.


*********************
* Using a .reg file *
*********************

Create a test file with the extension .reg. Place the following in that file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]
"BypassTPMCheck"=dword:00000001
"BypassSecureBootCheck"=dword:00000001
"BypassRAMCheck"=dword:00000001
"BypassStorageCheck"=dword:00000001
"BypassCPUCheck"=dword:00000001

Drop this registry file onto your install media. After starting setup, when you reach the first static screen where information is requested by setup, press Shift + F10 to open a command prompt. Navigate to the drive letter where the .reg file is located and then run it. Close the command prompt and continue installation of Windows as usual.


**********************
* Using a Batch File *
**********************

Create a text file with the extension .bat. Place the following in that file:

@echo off
reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f > NUL

NOTE: The "> NUL" simply suppresses the output from being displayed for "silent" operation.

Drop this file onto your install media. After starting setup, when you reach the first static screen where information is requested by setup, press Shift + F10 to open a command prompt. Navigate to the drive letter where the .bat file is located and then run it. Close the command prompt and continue installation of Windows as usual.

I've read all of these things and tried them Many of them resulted in a failure to work because of MBR partitions. It would be trivial to wipe the partitions but my goal was to keep the data on the drive. Obviously I did something wrong until I did it on a supported computer. At this point I have all the systems running Win 11 that I want running it and I won't need to fuss with it again unless I buy a refurbished computer in the future. It took longer than necessary but time runs pretty quickly at my age.

I'm running Windows 11 on 10+ year old systems with MBR. No problem. Appears to run even better than Windows 10 did :)

hsehestedt said:

I'm running Windows 11 on 10+ year old systems with MBR. No problem. Appears to run even better than Windows 10 did :)

Click to expand...

For how long though? I'm betting the time for that will run out sooner than support for Win 10 does.

Dch48 said:

For how long though? I'm betting the time for that will run out sooner than support for Win 10 does.

Click to expand...

It's possible, but I fully assume that risk.

Dch48 said:

For how long though? I'm betting the time for that will run out sooner than support for Win 10 does.

Click to expand...

Only MS can say for sure. My guess and only a guess is that unsupported devices will still be able to run. They just won't be able to update.

Winuser said:

Only MS can say for sure. My guess and only a guess is that unsupported devices will still be able to run. They just won't be able to update.

Click to expand...

Right now, I'm willing to bet that not even MS can say for sure!

As everyone here has stated, only MS knows. There's got to be a reason the requirements have been put in place in the first place when we all know Windows 11 runs just fine without any of the requirements. One would think MS would not alienate their customer base by making some drastic decision in the future, but we've got to remember it's MS we dealing with. Their track record has not always been favorable, but they've never once shut the OS down if it wasn't supported. I'll bet they have something up their sleeve though. But one can look at it in another way as well. Why would they leave all the holes that let folks install Win11 on incompatible hardware in the first place? Just like why have they left the door open for all the tweaks we do. They could have locked this OS down tighter than Dick's hatband.

NavyLCDR said:

What I find especially humorous is the users that upgrade to Windows 11 and then install all kinds of hacks and apps to make it look like/act like Windows 10

Click to expand...

Hell I install hacks so windows looks like windows 95 so go figure. There are only three reasons I change OS's. 1 MS drops support for the OS I'm using, 2 The new OS has added functionality I have a need for or 3 I need to know how to navigate and operate a new OS so I can help out friends and relatives. IMO each new OS is more dumbed down than the last and soon we will wake up running mac's. MS must also have a click quota as every new OS adds as many additional clicks to get to a given setting as possible. MS should change its name to Antilogic!

Wonderwrench said:

Hell I install hacks so windows looks like windows 95 so go figure. There are only three reasons I change OS's. 1 MS drops support for the OS I'm using, 2 The new OS has added functionality I have a need for or 3 I need to know how to navigate and operate a new OS so I can help out friends and relatives. IMO each new OS is more dumbed down than the last and soon we will wake up running mac's. MS must also have a click quota as every new OS adds as many additional clicks to get to a given setting as possible. MS should change its name to Antilogic!

Click to expand...

LOL

I saw your account name in teeny font on the far right of the "What's New" page of the forum.
So I clicked on it and rushed to this topic/post to who "Wonderwench" was.
Once I saw the R in Wonderwrench... well it was a let down.

england66 said:

Reality has set in , I won't be updating to windows 11 anytime soon.
In addition to the above changes I cannot myself accept the changes to file explorer or the right click menu. As things stand I can't think of anything positive to say about Windows 11

Click to expand...

Hi there
Why not "Dual boot" W10 and W11

Create EFI formatted FAT32 100 mb, MSR not formatted 128mb and single large partition (ntfs) on "C" drive (having backed your Windows system first.

Create 2 vhdx files, 1 each for windows 10 and 11 -- note these are NOT VM's and HYPER-V etc is not required so method also works on Windows HOME editions.

boot from Macrium free stand alone recovery or whatever recovery / imaging software you have and select the command mode

diskpart
select disk xxx
list vol
select vol xxx where xxx is the efi partition (usually shown as SYSTEM HIDDEN
assign letter=

create vhdx file=D:\W10.vhdx etc
attach vdisk
list disk
select disk yyy --- that's the vhdx attached
create partition primary
format fs=ntfs quick (VHDX boot doesn't need EFI -- the main disk has the EFI partition)
assign letter = w
exit

now restore your W10 system to W:

you have also to re-write the Windows boot mgr so get into the console command again

so cd w:\windows\system32

bcdboot w:\windows \s S: /f UEFI

now boot W10 -- should boot

for W11
from WITHIN W10

create another vhdx file W11.VHDX and assign and create an NTFS partition on it and assign S to the system EFI partition. Assume the W11/vhdx file is on W and W11 iso on E. You can get the iso from uupdump easily enough.

Now the install

dism /Apply-Image /ImageFile:E:\sources\install.wim /index:1 /ApplyDir:W:\
cd w:\windows\system32
bcdboot w:\windows /s S: /f UEFI

on boot you should then see choice of W10 and W11. Easy way of "physical dual boot" instead of messing about with loads of partitions, EFI stuff etc etc.

I have a ton of stuff on W11 currently and I've only allocated maximum size for the vhdx file (the "C" disk as 60 GB of which I've only used 42GB.



W11 IMO seems to be a lot snappier than W10 and in any case good for testing real hardware. Done this way you've got choice of W10 or W11 without a load of backups and restores each time you want to change the OS and you can easily compare software running on W10 with same stuff on W11.

I've got all this lot available on a quite modest laptop : (2 versions of W11 -- one Eng, one Icelandic), W10, Windows server 2022 (180 day free trial so I can learn about and play with a Windows server) and GRUB which boots an Arch Linux distro.



with also a LINUX OS as well available from the boot menu -- move mouse to change defaults / other options : (GRUB)



In any case always keep OS separate from data files e.g multi-media, office documents, email data etc etc. That way you can keep the OS disk small and if it goes pear shaped you don't have to mess around recovering user data.

Cheers
jimbo

FYI I just upgraded Windows 10 Pro 21H2 to Windows 11 Pro on the system listed in my profile yesterday. Asus claims the motherboard is Windows 11 ready. TPM was enabled by default but secure boot is not and is set to legacy OS. Windows 11 installed fine and has no complaints even though secure boot is still not enabled and set to legacy OS. I'm getting windows updates so I'm going to leave it be as its nice to boot up in less than 15 seconds.

Ghot said:

LOL

I saw your account name in teeny font on the far right of the "What's New" page of the forum.
So I clicked on it and rushed to this topic/post to who "Wonderwench" was.
Once I saw the R in Wonderwrench... well it was a let down.

Click to expand...

Sorry to disappoint! Years ago it got very difficult to come up with a forum name that was not already used. I worked as an auto technician and was given the name by another technician.

The story goes if you care to hear it. I was working in a small shop and was the low man on the pole. I was given a water pump job on a ford pinto (easy job). The head tech was given a water pump on a dodge van (pain in the ars). The head tech cried to the owner and I was given the van instead. I was ****** off and worked as hard as I could and finished the van before the head tech finished the pinto. The number 2 tech came up to me and said "you are a freaking wonder wrench". From that day forward the name stuck even though I thought of my self as a common mortal. Once I left this shop I never used this nick name again.

I later found that the Wonderwrench nick works well online as it is uncommon so I use it everywhere I can. If you see the nick some place else its most likely me though there are a few copy cats out there.

Well, I think the story for Wonderwench, might have been better.

fmw said:

I've read all of these things and tried them Many of them resulted in a failure to work because of MBR partitions. It would be trivial to wipe the partitions but my goal was to keep the data on the drive. Obviously I did something wrong until I did it on a supported computer. At this point I have all the systems running Win 11 that I want running it and I won't need to fuss with it again unless I buy a refurbished computer in the future. It took longer than necessary but time runs pretty quickly at my age.

Click to expand...

I updated 2 machines, old and neither had TPM, and it worked flawlessly. This simple set of instructions worked like a charm, leaving all programs and data. See this link, post # 266.

Update on Unsupported Equipment

But after working with Win 11 I'll keep it on my laptop but Win 11 isn't really an upgrade as much as it is a GUI update. So if you have a machine you're happy with and really just use the machine for productivity rather than for the fun of tweaking, I'd just leave it alone.
John