Forum Discussion
Windows 10 boot hangs on “Preparing Automatic Repair.” “bootrec /fixboot” Access is Denied
I found this old post when looking for "CCCOMA_X64F" (Win10), as the only mention of it in these forums, I didn't get far. And I assume the poster has long moved on. Worst case scenario is that the SSD was dead. But before diagnosing that, we'd need to know whether the BIOS was set to boot UEFI or "legacy", usually found by pressing F12 at boot. This time it seems "EFI" is expected. Then the formats of the existing partitions need to be discovered. Invoke diskpart from the command line, then "list volumes". Is the filesystem (fs) of the EFI boot partition (apparently D: in this case) FAT32? Is C: NTFS? Anything else would be problematic, and reformatting called for. Hidden NTFS? This is a sneakier problem. I usually use a GParted bootable disk (free), https://gparted.org/livecd.php with a graphical interface to fix such problems. Various other "Partition Managers" from bootable media are available and usually from a bootable medium, and many with Free Trial versions, and also with graphical interfaces making it easy to visualize operations, and specifically, multiple partitions on disks. If diskpart from a CCCOMA_X64F boot disk is your only tool, and no partitions or disks are detected- Most likely you have a dead disk, and your only option is to replace it.
cuvtixo Usualy some hacker service_garbage -p in ram started and locks the hack.
It might also be a process in ram that protects the service_garbage.
Look in register for _garbage and you see lots of them startup=4 disables prevents starting. Immage is the file somewhere on storage thats the problem.
So some or many service_garbage keys after a service acting different than the service_garbage start manually and thats is not 4.
When you power down the hack stays in ram.
When you shut down, the hack dumps on storage and takes time.
When for boot up, the hack has to load a 64KB and 3GB in ram to work.
After deleting all files unlocked there remained a C:\SYSTEM~1\
No windows 10 map of about 3GB.
There remains also a 64KB file.
After a reboot microsoft hides both out of sight.
I had to recover with setup.exe
