New
#21
However, Windows 10 uses a different "Compact OS" method than WIMBOOT and does not require an image or recovery partition for it.
However, Windows 10 uses a different "Compact OS" method than WIMBOOT and does not require an image or recovery partition for it.
Causes aside, all of the drives are hidden, GPT type and report differently in Aomei or Minitool whether they are empty or full. And nothing seems to be able to delete the partitions. Ergo there's something corrupted in the partition tables or whatever GPT uses - maybe a single GUID is wrong somewhere.
What else can be tried?
Attempt recovery using Recuva?
Attempt to assign drive letters?
Convert disk from GPT to MBR?
Use a low level editor to examine what's actually present below the apparent empty structure, a hex editor, or perhaps tools like RWEverything or Spinrite?
If you look for causes, is this damage viral? Could an antivirus discover something lurking that is corrupting the low level format of the storage medium?
The only thing I can suggest is make an image of a minimal Windows 10 install from another computer (same version you want on the tablet), just the Windows partition, then restore that image to the large space on the tablet. Macrium Reflect Free would be good for that. Hopefully the boot partition on the tablet will boot the Windows 10 once it is copied over from the image. Then you can run the command to compact the OS - and you should be able to use showkey to retrieve the Windows 8 product key from the bios and use that to activate the Windows 10 you copy over.