Windows clean install-sufficient hard disk storage space. Error 0x800700EE

Jeg legger meg inn i denne tråden og kan vise til dette resultat:

DISKPART> list vol

Volume ### Ltr Label Fs Type Size Status Info

Volume 0 J DVD-ROM 0 B No Media

Volume 1 C BOOT DISK C NTFS Partition 930 GB Healthy Boot

Volume 2 NTFS Partition 589 MB Healthy

Volume 3 NO NAME FAT32 Partition 100 MB Healthy System

Volume 4 F FastDisk 2A NTFS Partition 931 GB Healthy

Volume 5 I O- 4TB WD-G NTFS Partition 3725 GB Healthy

Volume 6 P FAT32 Partition 7635 MB Healthy

Volume 7 L BACKUPPER FAT32 Partition 14 GB Healthy

Volume 8 G Removable 0 B No Media

Volume 9 K 18TB PROSHO NTFS Partition 16 TB Healthy

Volume 10 H Kommende I NTFS Partition 5589 GB Healthy

Volume 11 D PROSHOP 6.1 NTFS Partition 16 TB Healthy

Volume 12 T 22.10.22 PR NTFS Partition 5589 GB Healthy

Volume 13 E HGST 6TB 1 NTFS Partition 5589 GB Healthy

Volume 14 M 4TB WD-GOLD NTFS Partition 3725 GB Healthy

Volume 15 N ComputerS 4 NTFS Partition 16 TB Healthy

Volume 16 O IMAGE_C_19. NTFS Partition 930 GB Healthy

Volume 17 NTFS Partition 589 MB Healthy

DISKPART>

Vol1 er min boot disk, i motsetning til vol4 som er et image kopi av OS, backup utført av MS Backup og recovery app.

MEN, før jeg i det hele tatt kan benytte meg av bcdeit, jeg vil trenge å få bort denne meldingen:

C:\Users\Administrator>bcdedit

The boot configuration data store could not be opened.

Volumet for en fil er endret eksternt, slik at den åpnede filen ikke lenger er gyldig.

C:\Users\Administrator>

Lengre og forbi at dette stadiet fremdeles er representert, befinner jeg meg per i dag ikke.

Thank you, Ramesh. I like that article you posted...

https://www.winhelponline.com/blog/rebuild-efi-partition-bcd-boot-files/ How to Rebuild the EFI Boot Partition, BCD and Boot Files

(a) But step 2 (that uses BCDEdit) will likely also fail in the recovery environment. So, to find the letter that the Windows partition has, use List Vol...

DiskPart

List Vol <<<List volumes & letters

Exit

His Windows partition will look like the following, but may have a different letter...

Volume 1     C   BOOT DISK C  NTFS   Partition    930 GB  Healthy    Boot

Use that letter instead of E: that the article uses.

(b) The article doesn't move EFI to be the first partition on Disk 0, & it doesn't give him an MSR. But neither may really be necessary.

You may try this in the meantime:

• robocopy Y:\EFI C:\EFI.BAK /MIR
• attrib -s -h -r Y:\EFI\Microsoft\Boot\BCD
• copy Y:\EFI\Microsoft\Boot\BCD C:\BCD.BAK
• del Y:\EFI\Microsoft\Boot\BCD /a
• bcdboot C:\Windows /s Y: /f UEFI

This rebuilds the BCD and boot files.

See if you run BCDEDIT now.

@PCR: Nice analysis. I'll await the results of those commands. Thought of doing #5 right away.

@Tage: See recommended partition layout (MSFT article)

My idea is to nuke Vol 3 or make it a regular partition without deleting it. Then shrink C by 500 MB, create a new EFI of size 500 MB, and rebuild the EFI Boot Partition, BCD and Boot Files. But suggest creating a system image backup of the OS and boot partitions using Macrium, beforehand.

(1) Because Windows Backup & Restore (B&R) is flaky for you, you should make an image with Macrium Reflect as well under Ramesh's guidance. I do use B&R after each new, monthly Windows OS Build comes in. But, for peace of mind, I make an image with Seagate's DiscWizard as well after each new Windows version comes in. But I don't think there will be any more.

(2) It is weird what is going on with BitDefender.

(a) Do you think they will get back to you on your ticket?

(b) Which does Windows Security say is the real-time scanner?

(3) My BCD is about 3 times your size...

Mine: 02/06/2023 04:49 AM 57,344 BCD

Yours: 07.02.2023 01:01 20 480 BCD

Let's see whether we can see yours this way, if its letter is still Y...

BCDEdit /Store Y:\EFI\Microsoft\Boot\BCD /Enum All

BCDEdit <<<Just to see whether it magically works now

(4)

(a) I can't understand why your MSInfo32 now shows...

Oppstartsenhet \Device\HarddiskVolume10

That would mean there is an EFI ten partitions down (as seen in DiskPart) counting from those on Disk 0. It makes me wonder whether I understand that rule at all since you don't appear to have one there. I only see one on Disk 0 now. But I think there's a wrinkle that, if you boot directly to an HDD (instead of to the BootMGR), it will start counting from that HDD. That's why I wanted to see the Firmware Boot Manager (FWBootMGR) which is a window to the BIOS Boot screen. It still can't explain the number ...10 though that I can figure.

(b) Can you unplug all your HDDs except Disk 0 & see whether it boots? If so, show us...

BCDEdit /Enum {fwbootmgr} <<<Show Firmware Boot Manager

BCDEdit <<<Show Windows Boot Manager & Boot Loader(s)

(5) I'm not sure it's safe yet to try to give you new EFI & MSR partitions.