never ending issues with w10 install-recovery needs repair

[inquisitor1]

made a post that I have issues with nvme drive. and doing RMA. so wanted to install w10 on sata ssd. and send nvme back. get files off I need off it and on sata ssd. so connected that ssd in. so basically there is an nvme drive connected and an empty sata ssd. windows 10 os is on a 120gb ssd used with usb connector. I used to install with rufus. so in bios changed boot to goto the usb sata ssd with w10. selected the internal connected sata ssd I wanted to install to. alls fine. I chose boot to be the new installed sata ssd. says recovery needs repair.

Error code 0xc000000e Your PC needs to be repaired. I have that exact code.

I tried to take out my sata ssd then boot from nvme. no go. same issue. tried f1 repair. no go. I tried to boot from usb/ssd with win10 to do a repair. no go. no option at the bottom left. only can do a new install. anyways, does this guide seem legit to deal with my issue?

I learned my lesson now and everytime Ill install win10 on another drive, ill take out any drive that has w10 on it. it does some weird things that has nipped me a few times.

any help appreciated

 

[Splinterdog]

In my experience, those 'Windows needs to be repaired' messages never end in anything good are usually a dead end.
When confronted with a similar situation and usually when I'm installing W10/11 on a system with multiple drives, I always disconnect the others until Windows is safely installed on the target drive.
Also, if there's nothing to save on the drive in question, ignore that video and just start from scratch.

 

[inquisitor1]

I have pictures there. I have a backup but on an HDD which will take ages to move over. were talking about 350gb

my intuition is right about the LEXAR nvme being defective. but I still want to try and want to know if what the guide says to type in cmd is correct and the right path?

I had this bs with installing w10 on a 2nd drive and it creating issues. I should have learned that you cant have 2 win10 installs together. I hate microsoft. never had issues with w7 ever. only issues with windows 10.

what about pulling the nvme out and putting it into a usb case and pulling files I need that way?

take nvme, install sata ssd. install w10 and drivers. connected nvme with usb case and pull files?

 

[Splinterdog]

I have pictures there. I have a backup but on an HDD which will take ages to move over. were talking about 350gb

my intuition is right about the LEXAR nvme being defective. but I still want to try and want to know if what the guide says to type in cmd is correct and the right path?

I had this bs with installing w10 on a 2nd drive and it creating issues. I should have learned that you cant have 2 win10 installs together. I hate microsoft. never had issues with w7 ever. only issues with windows 10.

what about pulling the nvme out and putting it into a usb case and pulling files I need that way?

take nvme, install sata ssd. install w10 and drivers. connected nvme with usb case and pull files?

If you really need those files and the NVMe isn't bust, try the USB case. I would.

 

[inquisitor1]

thanks SP. put it in the case and it seems I have access to files. will finish installing w10 on the sata ssd and transfer files over.

 

[DaemonForce]

You're operating from a bad stack.
1. Going into a recovery/migration situation completely unprepared
2. Trying to adapt a troubled system disk over USB adapter on the system that already has boot issues and
3. That disk is somewhere along the read/copy data migration chain.
Just...What?

Grab WinPE (WAIK/Win10)
Configure it to be useful on your system/network (add drivers, Explorer, WinNTSetup3, your own backup tools)
Burn WinPE to a throwaway 1GB USB stick using Rufus
Create an answer file and add it to the disk.
Boot WinPE on target system
Rearrange the desired data on your disks/network
Profit

No physical removal or shuffling of disks involved.
No reliance on the nvme's boot partition.
No rewiring of network kit involved.
No issues converting between BIOS/EFI or moving the computer here and there.
Just get it done and move on. Easy.

In situations where I need to setup Windows I often rely on something called WinNTSetup3. It looks like this:

On open, it auto-letters any boot volumes present, shows partition boot status and offers tools with BootICE.
It can be used to prepare drives and image the target partition with drivers and an answer file.
This cuts out ALL the drama, custom image build time and time wasted chasing this and that, as long as you provide a valid answer file.
Something tells me you're the type to see this situation a lot even if it's not your own computer.
Maybe position yourself with this kind of advantage for the future before you encounter it again?
I make a new WinPE like every 5-6 years and I'm real lazy about it compared to the XP era. I'm sure you can deal better than I do.
There are security reasons involved for doing all this work and it makes the entire recovery/install job that much more effective.

 

[micropage7]

have you try minimal setup, disconnecting anything that you don't need
resetting bios
you may face bad drive, bad installed OS, bad connector or just something refuse mix and match
edit: have you try different version of windows, just to check

 

[agent_x007]

1) Don't mix NVMe and SATA boot.
For Windows, NVMe needs GPT partition style with EFI boot selected to be valid boot option by default, while SATA drives can boot with either GPT/EFI and MBR/CSM options. Booting MBR with disabled CSM mode will not work. Booting NVMe in CSM might work if EFI booting is selected for storage devices.
2) In case of CSM disabled situation, make sure you are booting from Windows Boot Manager (in BIOS/UEFI).
Selecting actual drive in boot section will only work with CSM legacy/MBR drive.
3) Disable SATA devices when installing new Windows on NVMe, and switch off (if you can) M.2 ports when you want to install Windows on SATA SSD. It will prevent Windows installer from using wrong drive as boot sector holding one (Windows installer is dumb AF and can put boot files on detected SATA HDDs, even when actual OS is installed on NVMe - disconnecting SATA drive = no more NVMe OS boot).

 

[Splinterdog]

You're operating from a bad stack.
1. Going into a recovery/migration situation completely unprepared
2. Trying to adapt a troubled system disk over USB adapter on the system that already has boot issues and
3. That disk is somewhere along the read/copy data migration chain.
Just...What?

Grab WinPE (WAIK/Win10)
Configure it to be useful on your system/network (add drivers, Explorer, WinNTSetup3, your own backup tools)
Burn WinPE to a throwaway 1GB USB stick using Rufus
Create an answer file and add it to the disk.
Boot WinPE on target system
Rearrange the desired data on your disks/network
Profit

No physical removal or shuffling of disks involved.
No reliance on the nvme's boot partition.
No rewiring of network kit involved.
No issues converting between BIOS/EFI or moving the computer here and there.
Just get it done and move on. Easy.

In situations where I need to setup Windows I often rely on something called WinNTSetup3. It looks like this:
View attachment 354311
On open, it auto-letters any boot volumes present, shows partition boot status and offers tools with BootICE.
It can be used to prepare drives and image the target partition with drivers and an answer file.
This cuts out ALL the drama, custom image build time and time wasted chasing this and that, as long as you provide a valid answer file.
Something tells me you're the type to see this situation a lot even if it's not your own computer.
Maybe position yourself with this kind of advantage for the future before you encounter it again?
I make a new WinPE like every 5-6 years and I'm real lazy about it compared to the XP era. I'm sure you can deal better than I do.
There are security reasons involved for doing all this work and it makes the entire recovery/install job that much more effective.

I forgot about WinPe which I use all the time for rescues. Thanks for reminding us.

 

[Hardcore Games]

I keep old SATA SSD in USB-C boxes and more recently I now have old M.2 2280 SSD in USB-C boxes. So when it's time to reinstall Windows....

Use Windows 11, 10 is past its best before date. Rufus can get around CPU/TPU problems.