Windows 10: Files Inaccessible After Creating Boot USB

Hello,


I recently reinstalled Windows from a USB device. I used a USB device larger than required which had some files on that I couldn't store on the PC due to the intent to format the main hard disk.


After successfully reinstalling Windows, the USB device is now showing in Disk Management the 32Gb used for the installation files then a section of 'Free Space' and a section on 'Unallocated' space. From the size, it is the 'Unallocated' space that are my old files but despite trying a number of solutions found online, I have been unable to get these files recognised.


Any ideas would be much appreciated!


Thanks.

:)

 

Stop code inaccessible boot

Hi,

i created the installation media USB flash drive, what is the next step with the desttop system with inaccessible boot device.

Thanks,

Joe Marchesani Sr.

 

Windows 10 Reset (remove files, no disk wipe) fails with Inaccessible Boot Device; Defender Offline fails with 0x8007002

Two identical Dell Inspiron 660 systems (one for each child):

• Win7 --> Win 10 upgrades went uneventfully, normal function afterward.
• 1st system then put through Windows 10 Reset procedure with file removal AND disk wipe, completed successfully, normal function
• 2nd system then put through Windows 10 Reset procedure with file removal WITHOUT disk wipe --> procedure fails:
  • INACCESSIBLE BOOT DEVICE error is thrown, with an endless reboot cycle
• Based on
  this thread reference to
  KB2673509, Windows Defender Offline downloaded and run to create USB installation
• USB device inserted into affected system
• Boot device sequence manually directed to USB during reboot cycle via BIOS <F12> key function
• Windows Defender Offline initiates, but halts throwing error 0x8007002

• This code
  appears to be related to a problem with Windows update, which I can not rationalize given that this is explicitly an
  offline tool.

What are the suggestions for next step(s)?

 

Inaccessible boot device

This is a Microsoft link on inaccessible boot device:
https://docs.microsoft.com/en-us/win...le-boot-device

It is an intermediate level link.
There are more advanced steps that can be ran once the partition structure is known.
There are steps for repair of the boot sector, operating system, etc.
Sometimes this bugcheck can be caused by windows updates.

A reset save files equivalent may be able to be performed.
Alternatively a clean install can be performed once important files are backed up.