Alienware 14 Cannot Boot Disk Errors and USB External Recovery Errors Help

[RichiePri]

My brother's Alienware 14 Laptop is in a big predicament. After he "FORCED" Windows 10 into his pc, his pc has been acting very strange and has had poor performance. He wanted to reset so he tried, but windows wouldn't let him go into recovery settings and gives him an error when trying to access them. We tried another method of recovery that included the program of AlienRespawn that I downloaded from the website of Dell on MY Alienware (we both have alienwares) I installed it and used a samsung 1tb M3 Portable External Hard drive to put a factory recovery media onto, I then put it into my brother's broken alienware and it loaded up. the controls were a bit finicky, but I chose the option for factory reset using the media. When it was preparing the hhd on the PC not the external, it deleted everything off of it before displaying the message, "Recovery failed, check recovery media" or something like that. We tried reinstalling the media on the External Drive multiple times, checked the format, and reset the ext. drive and reinstalled it again, but no use. Is it because the Alienware I HAVE, has an SSD and the one MY BROTHER has has an HHD and it won't work cause im trying to recover a media from an SSD instead of HHD and they will not connect or what? Idk. Next I remembered that I had the windows 8 recovery media that came with the pc, but when I put it in, it was not recognized by the pc. I tried the windows 7 installation disc as well, but the same thing happened. The message that displays is that Windows failed to start and needs to be boot from recovery using a disc. It then lists the instructions on how to use the media. Then at the bottom it displays the file that has the error: EFI/Microsoft/Boot/BCD
Error 0x000000f
Windows has corrupted boot files or missing
It says something like that.
Is there anyway to get around this so I can install the recovery and get on his pc?
Is there anyway to fix the alienrespawn from causing an error?
Why isnt it recognizing the disks?
UPDATE:
the windows 7 install disk and windows 8 recovery are recongnized, but you have to go into the UEFI setup and select them from there. They work until.... WOW I have the worst luck
The windows 7 wont install because of a security police error on UEFI and windows 8 recovery want install because there are no drivers to install for some reason idk im so confused.
Thanks for the help, Richard

 

[Colif]

download this - windows media creation tool

What I suggest is download that tool and let it create a win 10 DVD or USB (depends what you have) as its much more useful than a win 7 or 8 installer.

instead of using recovery, download all the drivers you need for pc onto a USB or something, and then use the win 10 installer to do a fresh install

if there is anything he wants off drive, you can use: https://www.winhelp.us/recover-files-using-puppy-linux.html

fresh install instructions: http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html

 

[RichiePri]

download this - windows media creation tool

What I suggest is download that tool and let it create a win 10 DVD or USB (depends what you have) as its much more useful than a win 7 or 8 installer.

instead of using recovery, download all the drivers you need for pc onto a USB or something, and then use the win 10 installer to do a fresh install

if there is anything he wants off drive, you can use: https://www.winhelp.us/recover-files-using-puppy-linux.html

fresh install instructions: http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html

Colif the problem is that the AlienRespawn program creates a WIN 10 Recovery, but when I load it up onto the broken pc and use factory reset option it just goes to an error message everytime and I tried many different things to try and fix it, but it doesnt work. I don't know why. It says Check recovery media. I have a samsung M3 External Drive 1tb and I used a pc with a ssd to make the recovery media. Does that mean that the ssd will not work cause Im trying to put the recovery from a ssd to a hhd (broken pc) ? Also when I use the windows recovery program to create a regular windows 10 recovery media guess what? It gives me an error that says Factory media could not be created! ERRRRR. Its so annoying. Is it because of the external drive is broken or creating errors? Idk
So I cant make a Windows 10 Recovery from Windows
I cant make a Alienware Dell Recovery for his pc
And use a win7 installation disk
I cant use a win8 recovery disk either!!!!
Whats is going on!!!!
Ok Im going to try to use a different tool to put the recovery media onto. a 16 gb usb flashdrive. Lets see if it works. I can only make a win10 one because I need 116gb for the Alienware one. ok here goes nothing.
Ok also how do I erase EVERYTHING off a external hard drive. Is it called formatting idk what to do.

 

[Colif]

the media creation tool creates windows 10 installation discs . Not recovery discs. You can fresh install win 10 using it. instead of messing around with recovery programs.

If you install win 10 and have all the drivers you need you can bypass much of the stages you trying to do

 

[RichiePri]

the media creation tool creates windows 10 installation discs . Not recovery discs. You can fresh install win 10 using it. instead of messing around with recovery programs.

If you install win 10 and have all the drivers you need you can bypass much of the stages you trying to do

Ok it worked. The windows 10 media thing worked, but I did something stupid after... I deleted the 4 recovery partitions because they were taking so much space from the hhd and I thought they weren't needed. I tried to reinstall windows, but I don't know If I'm supposed to uninstall windows then install again or something. I tried reseting the pc and reinstalling windows but the recovery partitions weren't being installed again. I made a big mistake. None of the Microsoft Corperation programs like XML or SQL frameworks or Visuals c+ were being installed. What do I do! There is no windows programs installed when I go to programs and features I don't see ANY programs. Also I did a scam with sfc and I found corrupt files, but were not able to fix them and gave me log files.

Logs:
2016-05-22 02:47:28, Info CSI 00004ea1 [SR] Verify complete
2016-05-22 02:47:28, Info CSI 00004ea2 [SR] Verifying 55 (0x0000000000000037) components
2016-05-22 02:47:28, Info CSI 00004ea3 [SR] Beginning Verify and Repair transaction
2016-05-22 02:47:29, Info CSI 00004ea4@2016/5/22:09:47:29.691 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004ea5@2016/5/22:09:47:29.691 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004ea6@2016/5/22:09:47:29.707 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004ea7@2016/5/22:09:47:29.722 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004ea8@2016/5/22:09:47:29.722 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004ea9@2016/5/22:09:47:29.738 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eaa@2016/5/22:09:47:29.754 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eab@2016/5/22:09:47:29.769 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eac@2016/5/22:09:47:29.769 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004ead@2016/5/22:09:47:29.785 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eae@2016/5/22:09:47:29.800 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eaf@2016/5/22:09:47:29.800 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb0@2016/5/22:09:47:29.816 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb1@2016/5/22:09:47:29.863 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb2@2016/5/22:09:47:29.879 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb3@2016/5/22:09:47:29.894 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb4@2016/5/22:09:47:29.925 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb5@2016/5/22:09:47:29.941 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb6@2016/5/22:09:47:29.957 Primitive installers committed for repair
2016-05-22 02:47:29, Info CSI 00004eb7@2016/5/22:09:47:29.972 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eb8@2016/5/22:09:47:30.04 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eb9@2016/5/22:09:47:30.019 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eba@2016/5/22:09:47:30.035 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ebb@2016/5/22:09:47:30.050 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ebc@2016/5/22:09:47:30.050 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ebd@2016/5/22:09:47:30.066 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ebe@2016/5/22:09:47:30.097 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ebf@2016/5/22:09:47:30.097 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec0@2016/5/22:09:47:30.113 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec1@2016/5/22:09:47:30.129 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec2@2016/5/22:09:47:30.144 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec3@2016/5/22:09:47:30.160 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec4@2016/5/22:09:47:30.160 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec5@2016/5/22:09:47:30.175 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec6@2016/5/22:09:47:30.191 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec7@2016/5/22:09:47:30.207 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec8@2016/5/22:09:47:30.207 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ec9@2016/5/22:09:47:30.222 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eca@2016/5/22:09:47:30.222 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ecb@2016/5/22:09:47:30.238 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ecc@2016/5/22:09:47:30.254 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ecd@2016/5/22:09:47:30.289 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ece@2016/5/22:09:47:30.310 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ecf@2016/5/22:09:47:30.311 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed0@2016/5/22:09:47:30.327 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed1@2016/5/22:09:47:30.327 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed2@2016/5/22:09:47:30.389 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed3@2016/5/22:09:47:30.405 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed4@2016/5/22:09:47:30.405 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed5@2016/5/22:09:47:30.421 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed6@2016/5/22:09:47:30.436 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed7@2016/5/22:09:47:30.436 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed8@2016/5/22:09:47:30.452 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ed9@2016/5/22:09:47:30.467 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eda@2016/5/22:09:47:30.483 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004edb [SR] Verify complete
2016-05-22 02:47:30, Info CSI 00004edc [SR] Repairing 2 components
2016-05-22 02:47:30, Info CSI 00004edd [SR] Beginning Verify and Repair transaction
2016-05-22 02:47:30, Info CSI 00004ede Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_10.0.10586.0_none_bc5203051efaaaaa\tahomabd.ttf do not match actual file [l:12]"tahomabd.ttf" :
Found: {l:32 giVNievUaqZjuvuay/eNED6QsgoRstKLUh/3ej1O8GU=} Expected: {l:32 oECJffR/X5tbSdlhKGDFKAH/l8a2lrb018M+ymongfk=}
2016-05-22 02:47:30, Info CSI 00004edf [SR] Cannot repair member file [l:12]"tahomabd.ttf" of Microsoft-Windows-Font-TrueType-Tahoma, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-22 02:47:30, Info CSI 00004ee0 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ck0Dsnqrz6RN6SPRau58uQHyXtGzrykDUsKoPgAr2KA=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-05-22 02:47:30, Info CSI 00004ee1 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-22 02:47:30, Info CSI 00004ee2@2016/5/22:09:47:30.514 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ee3 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_10.0.10586.0_none_bc5203051efaaaaa\tahomabd.ttf do not match actual file [l:12]"tahomabd.ttf" :
Found: {l:32 giVNievUaqZjuvuay/eNED6QsgoRstKLUh/3ej1O8GU=} Expected: {l:32 oECJffR/X5tbSdlhKGDFKAH/l8a2lrb018M+ymongfk=}
2016-05-22 02:47:30, Info CSI 00004ee4 [SR] Cannot repair member file [l:12]"tahomabd.ttf" of Microsoft-Windows-Font-TrueType-Tahoma, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-22 02:47:30, Info CSI 00004ee5 [SR] This component was referenced by [l:122]"Microsoft-OneCore-Fonts-DesktopFonts-windows-Package~31bf3856ad364e35~amd64~~10.0.10586.0.aa769378d5daebe8af8c9f1c3efdd70e"
2016-05-22 02:47:30, Info CSI 00004ee6 [SR] This component was referenced by [l:169]"Microsoft-Windows-Client-Features-Package-AutoMerged-windows~31bf3856ad364e35~amd64~~10.0.10586.0.Microsoft-Windows-Client-Features-Package-AutoMerged-windows-Deployment"
2016-05-22 02:47:30, Info CSI 00004ee7 Hashes for file member \??\C:\Windows\fonts\tahomabd.ttf do not match actual file [l:12]"tahomabd.ttf" :
Found: {l:32 giVNievUaqZjuvuay/eNED6QsgoRstKLUh/3ej1O8GU=} Expected: {l:32 oECJffR/X5tbSdlhKGDFKAH/l8a2lrb018M+ymongfk=}
2016-05-22 02:47:30, Info CSI 00004ee8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_10.0.10586.0_none_bc5203051efaaaaa\tahomabd.ttf do not match actual file [l:12]"tahomabd.ttf" :
Found: {l:32 giVNievUaqZjuvuay/eNED6QsgoRstKLUh/3ej1O8GU=} Expected: {l:32 oECJffR/X5tbSdlhKGDFKAH/l8a2lrb018M+ymongfk=}
2016-05-22 02:47:30, Info CSI 00004ee9 [SR] Could not reproject corrupted file [l:20 ml:21]"\??\C:\Windows\fonts"\[l:12]"tahomabd.ttf"; source file in store is also corrupted
2016-05-22 02:47:30, Info CSI 00004eea@2016/5/22:09:47:30.546 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eeb@2016/5/22:09:47:30.546 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004eec Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ck0Dsnqrz6RN6SPRau58uQHyXtGzrykDUsKoPgAr2KA=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-05-22 02:47:30, Info CSI 00004eed [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-05-22 02:47:30, Info CSI 00004eee [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-05-22 02:47:30, Info CSI 00004eef Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ck0Dsnqrz6RN6SPRau58uQHyXtGzrykDUsKoPgAr2KA=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-05-22 02:47:30, Info CSI 00004ef0 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 Ck0Dsnqrz6RN6SPRau58uQHyXtGzrykDUsKoPgAr2KA=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-05-22 02:47:30, Info CSI 00004ef1 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-05-22 02:47:30, Info CSI 00004ef2@2016/5/22:09:47:30.577 Primitive installers committed for repair
2016-05-22 02:47:30, Info CSI 00004ef3 [SR] Repair complete
2016-05-22 02:47:30, Info CSI 00004ef4 [SR] Committing transaction
2016-05-22 02:47:30, Info CSI 00004ef5 Creating NT transaction (seq 2), objectname [6]"(null)"
2016-05-22 02:47:30, Info CSI 00004ef6 Created NT transaction (seq 2) result 0x00000000, handle @0xb50
2016-05-22 02:47:30, Info CSI 00004ef7@2016/5/22:09:47:30.592 Beginning NT transaction commit...
2016-05-22 02:47:30, Info CSI 00004ef8@2016/5/22:09:47:30.686 CSI perf trace:
CSIPERF:TXCOMMIT;115420
2016-05-22 02:47:30, Info CSI 00004ef9 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2016-05-22 02:49:32, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2016-05-22 02:49:32, Info CBS TiWorker signaled for shutdown, going to exit.
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2016-05-22 02:49:32, Info CBS Ending the TiWorker main loop.
2016-05-22 02:49:32, Info CBS Starting TiWorker finalization.
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: ManifestCacheFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: CoreResourcesUnload
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: SessionManagerFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2016-05-22 02:49:32, Info CBS CbsCoreFinalize: WcpUnload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: DrupUnload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: CfgMgr32Unload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: DpxUnload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: SrUnload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: CbsEsdUnload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: CbsEventUnregister
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: AppContainerUnload
2016-05-22 02:49:33, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2016-05-22 02:49:33, Info CBS Ending TiWorker finalization.
2016-05-22 02:49:33, Info CBS Ending the TrustedInstaller main loop.
2016-05-22 02:49:33, Info CBS Starting TrustedInstaller finalization.
2016-05-22 02:49:33, Info CBS Ending TrustedInstaller finalization.

 

[Colif]

When you fresh install win 10 it would have deleted all the recovery partitions and replaced them with 4 it needs to run with, one of which is a recovery partition but it contains windows 10. It doesn't include all the drivers like your old recovery partitions, its used to reinstall windows. The drivers themselves are easily found on the internet now.

None of the Microsoft Corperation programs like XML or SQL frameworks or Visuals c+ were being installed. What do I do! There is no windows programs installed when I go to programs and features I don't see ANY programs.

this is unexpected. What did you do? did you delete partitions or something after the fact? were you confused about the missing partitions and do something??

you might be best just starting again and following this: http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html