Booting device not found - SSD visible in Bios but not in windows installer

[VH2000]

That looks good!

So now run cmd (admin)

and type (copy&paste the highlighted commands)

diskpart
list disk

(Is there a star (*) in the right column at disk 1? If yes continue
sel disk 1
list par
sel par 1
format quick fs=fat32 label="System"
assign letter="B"
exit
bcdboot D:\Windows /l en-US /s B: /f UEFI

exit

Ready ro bring it back to the other pc and insert carefully!

Enjoy

Edit: before you replace the disk type in this command:

sfc /offbootdir=D:\ /offwindir=D:\windows /scannow

[Alf_It]

Hi

if I well understood this will format the partition 1 as FAT 32. Why so?

The command bcdboot D:\Windows /l en-US /s B: /f UEFI 

is it for restoring the booting Uefi file or what?

mean time I have run chkdsk without any option, in read only mode, and I found 

Error detected in index $I30 for file 3B703.
Insufficient disk space to correct errors
in index $I30 of file 3B703

[VH2000]

The commands I gave you are correct! It has to be FAT32! I don't want to discuss the UEFI basics .

chkdsk /f /r D

If there is not enough space transfer some files to another disk.

Is there any hiberfil.sys on D:\ 

To see that you have to see hidden files

[Alf_It]

No, no hiberfil found on 😧

what does that mean?

[VH2000]

The hiberfil.sys is usually  appr. 5 GB or even more! 

On a system with a SSD drive there is no advantage for that.

It is to be deleted by

powercfg /H off

But you have to find files that can be deleted or transfered to a different disk.

Why is you Windows partition (D:) so full and at the limit that you can't run chkdsk? 

[Alf_It]

In the SSD there isn't just windows, but also several working documents

maybe a clean would be necessary

also because I think there might also be a window.old, need to recheck

I am now running again chkdsk

worst case I can even imagine to format it, and reinstall windows from the USB media.

Question is, if I format the SSD, will the laptop bios see it once I remounted it?

Otherwise the windows installer won't see it again.

What I still didn't understand is: since I can easily see it now trough the USB interface in an different pc, and I can access files etc, why wouldn't windows installer see it?

I can understand that it doesn't boot, if windows is corrupted, but the SSD itself should be seen by the windows installer, am I wrong?

[VH2000]

The windows installer detects it as a 0 MB disk. This can happen when the partition table is damaged.

But you can't format the drive and you can't initialize the disk. That creates a hidden MSR-Partition as startpartition!

You have to repair the bad sectors before you can run any installation!

When you run diskpart and type clean and no (!) other command you can use it for the new installation.

[Alf_It]

HI 

really thank you again for all your help, support and explanations, I really appreciate that.

I am not actually sure I understood your last sentence "When you run diskpart and type clean and no (!) other command you can use it for the new installation."

What do you mean by "type clean" ?

I didn't also get why I cannot just format flat the SSD, wouldn't this just clean up everything?

I did though get that I first have to repair the bad sector.

So I did run till the end the chkdsk and here below is what was found, please tell me what you think

chkdsk /f 😧
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
872960 file records processed.
File verification completed.
14751 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
8744 reparse records processed.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
Correcting error in index $I30 for file 3B703.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 3B703.
Sorting index $I30 in file 3B703.
1196368 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file WI61DE~1.CAT (3C8EC) into directory file 3B703.
Recovering orphaned file MI75F4~1.CAT (3CA7C) into directory file 3B703.
Recovering orphaned file MI6860~1.CAT (3CE2F) into directory file 3B703.
Recovering orphaned file microsoft-windows-tabletpcmath-package-Wrapper~31bf3856ad364e35~amd64~~10.0.19041.746.cat (3D181) into directory file 3B703.
Recovering orphaned file Microsoft-NanoServer-SystemUAP-Package~31bf3856ad364e35~amd64~sl-SI~10.0.19041.1320.cat (3D746) into directory file 3B703.
Recovering orphaned file Microsoft-NanoServer-SystemUAP-Package~31bf3856ad364e35~amd64~sk-SK~10.0.19041.1320.cat (3DBD2) into directory file 3B703.
Recovering orphaned file Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~pt-PT~10.0.19041.804.cat (3DCFF) into directory file 3B703.
Recovering orphaned file MI63AB~1.CAT (3DE34) into directory file 3B703.
Recovering orphaned file MI46FD~1.CAT (3DEC0) into directory file 3B703.
Recovering orphaned file MI63AC~1.CAT (3E001) into directory file 3B703.
Skipping further messages about recovering orphans.
328 unindexed files scanned.
328 unindexed files recovered to original directory.
0 unindexed files recovered to lost and found.
8744 reparse records processed.

Stage 3: Examining security descriptors ...
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
161705 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Adding 2 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

218418175 KB total disk space.
175207060 KB in 572762 files.
367836 KB in 161708 indexes.
8 KB in bad sectors.
963075 KB in use by the system.
65536 KB occupied by the log file.
41880196 KB available on disk.

4096 bytes in each allocation unit.
54604543 total allocation units on disk.
10470049 allocation units available on disk.

[VH2000]

Now excecute the commands I posted on 01-14-2022 06:14 PM‎

and try your luck 😉

[Alf_It]

Hi

sorry but the time stamps on the messages seems different,  I assume you refer to your message in which you wrote the command:bcdboot D:\Windows /l en-US /s B: /f UEFI   

right?

One question about that, running those commands will reinstate the booting of windows on the SSD? in this case windows will just boot as usual? or shall I still reinstall windows using the USB media?

mean time last night I also run twice another chkdsk using /r option, and in the end I have an unspecified error, but this error came right after the message "file data verification completed" of stage 4