Boot from USB .iso issues

Toggle sidebar Toggle sidebar
R

RhetoricalRabbit

Reputable
Dec 13, 2015
16
0
4,520
Recently moved house. Reassembled computer and had issues getting it to display anything beyond a black screen with the Windows message in the bottom right corner. I managed to get it to boot in Safe Mode and set it to do a restore. Came back to find out that the restore had failed and now having further issues as I cannot even gain access to Safe Mode.

As I was in Windows 7, I've opted to try and bring it back to life with Windows 10.

My now default load screen presents to me the following:

Code: 
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your compuiter."

If you do not have this disc, contact your system administrator or computer manugacturer for assistance.

Status: 0xc000000f

Info: The boot selection failed because a required device is inaccessible.

I'm now using a USB with a Rufus-readied Windows 10 .iso plugged in - displays as UEFI: (NTFS) Generc-USB3.0 CRW -SD (3740MB) - allows a boot to the installation screen as would be expected.

I have tried having a nose through these forums but there's such a proliferation of topics that I'm feeling it's a bit of wood for the trees here. Adding one that's hopefully more clearly labelled in its title and comprehensive in its detailing of the issue is my penance for planting another sapling ...

http://www.tomshardware.co.uk/faq/id-3128634/fix-automatic-startup-repair-loop-windows.html gives me

Code: 
The boot configuration data store could not be opened.
The requested ysstem device cannot be found.
http://www.tomshardware.co.uk/faq/id-3128552/fix-windows-error-boot-device-found.html gives me

Code: 
The type of the file system is NTFS.
Cannot lock current drive.
Windows cannot run disk checking on this volume because it is write protected.
Running as a fresh install - something I'd prefer to avoid if it can be helped as I'd like to be able to access my files if possible - allows me to get to the typical Upgrade / Custom screen.

Clicking Upgrade yields:

Code: 
The computer started using the Windows installation media. Remove the installation media and restart your computer so that Windows starts normally. Then, insert the installation media and restart the upgrade. (Do not select |Custom (advanced)| to perform an upgrade. |Custom (advanced)| installs a new copy of Windows and deletes your programs and settings.)
Going via Custom allows me access to a list of drives but they all have the notification that:

Code: 
Windows can't be installed on drive # partition #.
Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.
Option-tree the first exhausted, the Troubleshoot hierarchy also falls short.

Opting for the keep-file reset I am told:

Code: 
The drive where Windows is installed is locked. Unlock the drive and try again.
Similarly the wipe and reset informs me:

Code: 
Unable to reset your PC. A required drive partition is missing.
Heading into the advanced options:

System restore shares:

Code: 
To use System Restore, you must specify which Windows installation to restore.
Restart this computer, select an operating system, and then select System Restore.
Happily cmdprmpt functions as it should, although delving into that black mire is beyond my ken. The miscellaneous guides and attempts I've failed thus far however have the general trend of focusing around reassigning partitions and selecting disks. I may very well have been executing it incorrectly as some of my responses varied, but there have been a few dalliances in that quarter already with little return.

System Image Recovery, when the guidance has been clicked through (only one image available, I believe from the day I tried to rollback) I get this notification:

Code: 
Re-image your computer

The system image restore failed.

Windows cannot restore a system image to a computer that has different firmware. The system image was created on a computer using BIOS and this computer is using EFI.
UEFI Firmware Settings only allows me the option to restart my system.

Startup repair shares:

Code: 
Startup Repair couldn't repair your PC
Press "Advanced Options" to try other options to repair your PC or "Shut down" to turn of your PC.
Log file:
And that's a sic ending - no log file name was generated / displayed.

Finally, Go back to the previous build gives me:

Code: 
We ran into a problem and won't be able to take you back to the previous build. Try resetting your current build instead (Troubleshoot > Reset this PC).


So ...

Any takers? ^_^


Please & Thank-you
RR



EDIT:

As an addendum, I just ran through the commands from here - http://www.thewindowsclub.com/repair-master-boot-record-mbr-windows - including the nt60 all and I now have lost the UEFI option from the six, and gained the option to click on Windows 7 with the PC reset and keep screen. Although it still generates the same message.
Continuing to nose about to see if anything else has altered.

EDIT EDIT:

After clicking the option to Return to Windows 7, it has now returned the UEFI to the display, and removed the option to click on Windows 7 u.u
 
Solution
R



This has already been answered.

I have found a way to access my files whilst browsing. I found a huge file that I didn't recpgnise.
The size of my old hard drive.
Quick google as to the extension and I learnrd I could navigate to the vhd file of my old desktop and attach that as a virtual drive. Once done I right-clicked. Went to properties. Shared it amongst all accounts and that has enabled me to access my files.

Currently pulling them off. Hopefully this assists anyone in a similar quandry in the future. Once i have everything I need I'll format both disks and try a clean install using a USB 2.0 of Win10.
Thanks for...
Sort by date Sort by votes


Ah.
Thanks. Muchly ^_^
Will definitely try that.
I sadly can't test something this simple at the moment as pretty much everything is in storage - I went out to buy a new drive and got a 3.0 as quicker speeds seemed best for an install. Will go grab a 2.0 from my stuff in the morning and get back to you, although will have a rummage around and see if I can't dig one up from somewhere amongst my stuff I didn't store.

Hopefully it's just something that mediocre :)

As a precaution though - any other ideas peoples? ^.^
 
Upvote 0 Downvote
If you chose GPT partition in Rufus, that's why you're getting this error

Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.

You would have to delete all partitions / do a clean install to fix it.

Changing partition type to MBR in Rufus may fix it.
 
Upvote 0 Downvote



Aloha ^_^
Ah, danke.
I am 90% sure I went for MBR for BIOS and UEFI but as niggling thoughts are pushing that number down I'll run through it again.
Fresh install may help regardless :)

Thanks again for the input.


EDIT:

NTFS or FAT32?

I ran NTFS in my initial attempt.

I can't see it making much difference based on my - practically non-existant - knowledge of the two, but there were a couple of threads on here querying it whilst I was searching before making this thread.
Changing partition type to MBR in Rufus may fix it.

EDIT EDT:

FAT32 is incompatible with the .iso it seems.

exFAT something worth trying?
 
Upvote 0 Downvote




This is what I'm attempting. I ran Win7, and am now trying to get Win10 to be installed via the .iso, rather than through an upgrade.
 
Upvote 0 Downvote
No reason not to have NTFS on the Windows install stick, no idea if others are even supported. Why are you even trying? MBR or GPT is different thing, that was the problem.

If you can't make the repair install, maybe easiest sollution, is try buy new HDD or SSD, install fresh on it with only it connected, and once you got Windows up&running, install old disk and access/copy your files.
 
Upvote 0 Downvote


May have to come to that u.u




This is what I'm attempting. I ran Win7, and am now trying to get Win10 to be installed via the .iso, rather than through an upgrade.
 
Upvote 0 Downvote


No polite way to ask this really, but are you reading my posts? :/
Repeated querying of things already explained makes me wonder if you're not - is it something I need to address in how I'm putting forward the information ... ?

I can access the boot protocols but they refuse to resolve. It's outlined in the OP.

Currently mounting my Windows 7 to the USB 3.0 again and will try that to see if anything new arises.

Something to take up the time before I grab a 2.0 tomorrow - although my partner is wishing to drag me out on a walk u.u 🙁


EDIT:

Nope - no real change. Seems to just be Windows 7 variants of the above issues.

Which hopefully bolsters the chance of it being related to the drive ... but also of it being an internal hardware issue? :/

Running away for our walk now.

Thanks for what's been suggested thus far guys :)
 
Upvote 0 Downvote
It's all outlined in the original post.

I have now installed Windows 7. As a separate OS. When I boot I get the option to pick either Windows 7 or Windows 7.
The second leads me to the issues outlined above. The first to a fresh install.

In this install however I cannot connect to the internet. So further / alternate issues.

Is there a way to pull up my files and bring them across to the new OS?
And any suggestions as to why I can't find any network?
 
Upvote 0 Downvote
If you're using wireless, install the wireless drivers.

If you want to remove the other Win7 that doesnt work, boot into the good Win7 go to start type in msconfig.

Go to the boot tab. Select the good Win7. Select it make it the default OS

Select the stuffed stuffed Win7. Delete the entry

Does the other Win7 appear in disk management?? If it does give it a letter.
 
Upvote 0 Downvote
Inrin my internet through ethernet via BT flex.

Worked fine in the Safe Mode mentioned in original post.

The new OS is already listed as the default.
I installed ot on my C drive. I have the other installed on my SSD (D:).

Will deleting it from there remove it entirely? Or just from the boot process? Are there other ways to access the data? I'd rather not remove the access at this point as I've still to try using a USB 2 0.

 
Upvote 0 Downvote
I don't wish to format whilst there's a chance I can recover the data.

They both appear in DM.
HDD as C: which is where the bootable but not able to connect online system is
SSD as D: where the non-bootable but previously able to connect system is.

 
Upvote 0 Downvote



This has already been answered.

I have found a way to access my files whilst browsing. I found a huge file that I didn't recpgnise.
The size of my old hard drive.
Quick google as to the extension and I learnrd I could navigate to the vhd file of my old desktop and attach that as a virtual drive. Once done I right-clicked. Went to properties. Shared it amongst all accounts and that has enabled me to access my files.

Currently pulling them off. Hopefully this assists anyone in a similar quandry in the future. Once i have everything I need I'll format both disks and try a clean install using a USB 2.0 of Win10.
Thanks for the suggestions guys.
Muchly.

Hope this helps others, and that I won't be back posting in this thread ... 😛

Although I imagine I'll end up making another soon enough u.u
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom