[oh OK so if other pc Is UEFI and secure boot set sick pc to the same?
QUOTE=MaloK;2362638]Keyboard less operation was an option to prevent computer running windows NT4 to lockup at ntldr if no keyboard was connected.
Do you have another computer you could use to make the first part of the install on the SSD then swap it in the Machine and try to let it continue ?[/QUOTE]
Yes, you can disable secureboot, but the other option MUST be the same SATA /AHCI / UEFI / CSM etc...
Hi @bartjunited
I have the exact same problem with my lenovo machine. Did you managed to get it back to work? If so, how? With these steps(?):
Take hdd out of sick pc
And connect this to other pc
Boot from usb
Let it load the files
When it reboots to do the next part of the install on power off pc
Connect the hdd back to original pc
Set other pc to csm and turn off secure boot
Sooo..... all I know is this. MBR can ve converted to GPT anytime.
Rather then MCTool I would use W10PE eddition format the drive to your desired format. I would start with MBR. However if MBR is not supported I would go to GPT.
A problem with many late ( current ) computers is when you install an OS it adds it to a list in the BIOS as the designated OS. Just to mention.
Your machine is not sick it is just securing itself to the original installation. As somebody mentioned before you could go through the entire installation on any machine and then bring that same install to your current machine.
I have no idea why you have to use the MCT for this install??? I would just rufus an iso to usb load from usb and format then install. It just seems your BIOS has security settings on it and or for some reason the other operating system might be getting in the way.
Another option is to boot a test environment of linux and format the drive to whatever partition you want and then exit linux and pop in your install "disc" ( USb ) boot from USB go through the installer ( possibly format ) and then boot again from USB ( because sometimes the installer did not install the necessary operating system files.
Again if your booting into the primary drive and there is another operating system., chance is that it has been scrambled by your install. So you should use W10PE ( or linux via test run ) to format the drive ( erase and format to whatever format you want or erase and let the installer do it's job ).
Back to the BIOS. Again the BIOS "could be" securing itself as it is meant to do so. All if not most Think pads ( Lenova ) machines are this way as they are business machines.
I found a solution...
I had the same problem for months now.
Just download the iso-file of the windows 10 version 1909 and install it via rufus onto a min 8GB-Stick. (Here you can download the iso-file: Windows 10 Version 1909 - English 64-bit ISO : Microsoft : Free Download, Borrow, and Streaming : Internet Archive) Then install windows with this stick in a normal maneer.
Once you've installed windows (wich should with this stick work fine), download a bios-update exe-file from the official lenovo website: BIOS for Windows 10 (64-bit) - ideacentre 310S-08ASR - Lenovo Support DE
Just run the exe file and answer all querys with "no" except the "would you like to continue with bios-update" (or something like that). Once the bios update is completed, you can continue in windows and try to download the update-assistant for windows 10 version 22h2: https://www.microsoft.com/de-de/soft...load/windows10
run the update assistant, proceed the update like you would do at any other computer.
...aaaaannndddd; there you go. You have installed Windows 10 22h2 and can work with the desktop-machine again.
Nice one unfortunately I ended up giving the pc back to the customer. But this is great to know for next time
Quote