FYI
I have just updated an eligible Dell Latitude 5300 laptop from Windows
10 Pro to Windows 11 Pro using Windows Update.
No Microsoft account was required or requested & the ethernet cable was removed on the 1st reboot, so an internet connection not required after
the upgrade files had been downloaded.
Programmes previously installed (not many) ran ok & all desktop icons remained in place.
wasbit wrote:
FYI
I have just updated an eligible Dell Latitude 5300 laptop from Windows
10 Pro to Windows 11 Pro using Windows Update.
No Microsoft account was required or requested & the ethernet cable was
removed on the 1st reboot, so an internet connection not required after
the upgrade files had been downloaded.
Programmes previously installed (not many) ran ok & all desktop icons
remained in place.
Thanks, Wasbit. Nice to know it can be done like that. I'm still holding
off though. I keep reading too much bad stuff about 11.
FYI
I have just updated an eligible Dell Latitude 5300 laptop from Windows
10 Pro to Windows 11 Pro using Windows Update.
No Microsoft account was required or requested & the ethernet cable was removed on the 1st reboot, so an internet connection not required after
the upgrade files had been downloaded.
Programmes previously installed (not many) ran ok & all desktop icons remained in place.
On 6/16/2024 5:01 AM, wasbit wrote:
FYI
I have just updated an eligible Dell Latitude 5300 laptop from Windows 10 Pro to Windows 11 Pro using Windows Update.
No Microsoft account was required or requested & the ethernet cable was removed on the 1st reboot, so an internet connection not required after the upgrade files had been downloaded.
Programmes previously installed (not many) ran ok & all desktop icons remained in place.
I did something siimilar awhile back. I made a copy of my Win10 install
on a laptop, set that up in dual boot with BootIt, then updated one
of them to Win11. I can now boot either. I only want Win11 for testing software, so it works well for me. Though it's a bit odd. BootIt now gives
me a menu for 10 or 11 that seems to be coming from Win10. Then if I
choose Win11 it reboots into Win11. But at least it works. It seems
that Windows messes around with other Windows installs with EFI boot.
Which doesn't surprise me. Windows has always been nosey about dual
boot. I put Suse15 on another Win10 computer and BootIt handles both
without any complications.
The Windows provided "boot tiles", if you change from
the "default" OS, it requires a "double-boot" before
your OS comes up.
If you convert the boot menu into WinXP black screen
with text, the OS choices are treated equally, and only
one boot cycle is required to start either choice.
You can still define a default OS choice (for a hands-off boot).
Administrator terminal:
bcdedit /set {bootmgr} displaybootmenu True
To remove that later if you want
bcdedit /deletevalue {bootmgr} displaybootmenu
On 6/17/2024 2:51 AM, Paul wrote:
The Windows provided "boot tiles", if you change from
the "default" OS, it requires a "double-boot" before
your OS comes up.
If you convert the boot menu into WinXP black screen
with text, the OS choices are treated equally, and only
one boot cycle is required to start either choice.
You can still define a default OS choice (for a hands-off boot).
Administrator terminal:
bcdedit /set {bootmgr} displaybootmenu True
To remove that later if you want
bcdedit /deletevalue {bootmgr} displaybootmenu
Interesting. So Windows goes thorugh all that song and dance
in order to load enough libraries to show me WinRT? It's silly,
but a neat trick. It somehow bypasses BootIt on the next boot,
without replacing BootIt as the default. Now that I think of it,
I've never noticed whether choosing Win11 results in a full
reboot or just a kind of vomit-and-gulp action with system
libraries.
On 6/17/2024 8:27 AM, Newyana2 wrote:
On 6/17/2024 2:51 AM, Paul wrote:
The Windows provided "boot tiles", if you change from
the "default" OS, it requires a "double-boot" before
your OS comes up.
If you convert the boot menu into WinXP black screen
with text, the OS choices are treated equally, and only
one boot cycle is required to start either choice.
You can still define a default OS choice (for a hands-off boot).
Administrator terminal:
bcdedit /set {bootmgr} displaybootmenu True
To remove that later if you want
bcdedit /deletevalue {bootmgr} displaybootmenu
Interesting. So Windows goes thorugh all that song and dance
in order to load enough libraries to show me WinRT? It's silly,
but a neat trick. It somehow bypasses BootIt on the next boot,
without replacing BootIt as the default. Now that I think of it,
I've never noticed whether choosing Win11 results in a full
reboot or just a kind of vomit-and-gulp action with system
libraries.
Are you referring to Fast Startup ? That's where the kernel is
hibernated, rather than kernel + session, to give a faster boot
time.
On 6/17/2024 10:20 AM, Paul wrote:
On 6/17/2024 8:27 AM, Newyana2 wrote:
On 6/17/2024 2:51 AM, Paul wrote:
The Windows provided "boot tiles", if you change from
the "default" OS, it requires a "double-boot" before
your OS comes up.
If you convert the boot menu into WinXP black screen
with text, the OS choices are treated equally, and only
one boot cycle is required to start either choice.
You can still define a default OS choice (for a hands-off boot).
Administrator terminal:
bcdedit /set {bootmgr} displaybootmenu True
To remove that later if you want
bcdedit /deletevalue {bootmgr} displaybootmenu
Interesting. So Windows goes thorugh all that song and dance
in order to load enough libraries to show me WinRT? It's silly,
but a neat trick. It somehow bypasses BootIt on the next boot,
without replacing BootIt as the default. Now that I think of it,
I've never noticed whether choosing Win11 results in a full
reboot or just a kind of vomit-and-gulp action with system
libraries.
Are you referring to Fast Startup ? That's where the kernel is
hibernated, rather than kernel + session, to give a faster boot
time.
No. I don't mean anything like that. Just normal boot. It boots
to BootIt. I just tried it again.
When I select Windows 10 I get the two tiles options
for Win10 and 11. If I choose Win10 it goes into Win10. If I choose
Win11 it reboots completely, asks for my BIOS password, shows
BootIt again, then goes into Win11. Looking in the EFI partition I
don't see two folders for Windows, so I don't seem to be able to
just put each on the Bootit menu directly. It appears that the
EFI boot config is defauted to Win10 and switched if I choose
Win11. Yet on next boot it's still defaulting to Win10. What I
expected was two folders like microsoft.001 and microsoft.002,
so that I could just direct Bootit to one for Win10 and the other for
Win11.
On 6/16/2024 5:01 AM, wasbit wrote:
FYI
I have just updated an eligible Dell Latitude 5300 laptop from Windows
10 Pro to Windows 11 Pro using Windows Update.
No Microsoft account was required or requested & the ethernet cable
was removed on the 1st reboot, so an internet connection not required
after the upgrade files had been downloaded.
Programmes previously installed (not many) ran ok & all desktop icons
remained in place.
I did something siimilar awhile back. I made a copy of my Win10 install
on a laptop, set that up in dual boot with BootIt, then updated one
of them to Win11. I can now boot either. I only want Win11 for testing software, so it works well for me. Though it's a bit odd. BootIt now gives
me a menu for 10 or 11 that seems to be coming from Win10. Then if I
choose Win11 it reboots into Win11. But at least it works. It seems
that Windows messes around with other Windows installs with EFI boot.
Which doesn't surprise me. Windows has always been nosey about dual
boot. I put Suse15 on another Win10 computer and BootIt handles both
without any complications.
My main OS is Windows 8.1 installed on an NVMe M.2 drive
PC is a Dell Optiplex 3050 SFF
Windows 10 & 11 are installed on a partitioned NVMe M.2 drive mounted on
a PCIe adaptor card
Boot options are controlled by Easy BCD
- https://neosmart.net/EasyBCD/
On 6/18/2024 5:11 AM, wasbit wrote:
My main OS is Windows 8.1 installed on an NVMe M.2 drive
PC is a Dell Optiplex 3050 SFF
Windows 10 & 11 are installed on a partitioned NVMe M.2 drive mounted on a PCIe adaptor card
Boot options are controlled by Easy BCD
- https://neosmart.net/EasyBCD/
I guess I'm getting too old for this. I still haven't managed
to figure the BCD system. It used to be so easy when all
I needed to do was to edit a boot.ini file to point it to the
bootloader. I know about EasyBCD. I just haven't had any
luck figuring out how to work it.
On 6/18/2024 5:11 AM, wasbit wrote:
My main OS is Windows 8.1 installed on an NVMe M.2 drive
PC is a Dell Optiplex 3050 SFF
Windows 10 & 11 are installed on a partitioned NVMe M.2 drive mounted
on a PCIe adaptor card
Boot options are controlled by Easy BCD
- https://neosmart.net/EasyBCD/
I guess I'm getting too old for this. I still haven't managed
to figure the BCD system. It used to be so easy when all
I needed to do was to edit a boot.ini file to point it to the
bootloader. I know about EasyBCD. I just haven't had any
luck figuring out how to work it.
I don't understand. It's a GUI programme not command line.point I tried adding a mirror image of Win10 on my
Does this help?
- https://neosmart.net/wiki/easybcd/basics/
I've used it. I just don't get all the options. At one
On 6/19/2024 4:41 AM, wasbit wrote:
point I tried adding a mirror image of Win10 on my
I don't understand. It's a GUI programme not command line.
Does this help?
- https://neosmart.net/wiki/easybcd/basics/
I've used it. I just don't get all the options. At one
second SSD to my BootIt menu. I couldn't work out
how to do the edit. And the BCD file seems to hold a lot
of detritus to sort through. Maybe I find it difficult
because I don't actually understand the structure and
mechanism of new boot methods. No matter. So far I'm
getting by OK without it.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 361 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 123:21:27 |
| Calls: | 7,716 |
| Files: | 12,861 |
| Messages: | 5,727,955 |
