Solved Jump Drive with Win 8.1 pro will not install on new ssd

[KYHI]

Now I will explain - that decrypt file is the file that is used to create the windows setup media - be it used for the iso or usb media

but what the tool also does when it creates the windows media ISO or USB it encrypts the install.wim, thus you end up with an install.esd in the sources folder on the media and a megadata file..

We are going to use another program to create the installation media - thus we are doing away with the encryption process, so we can get a usable install.wim file

 

[sparhawk]

The installer give error and every thing was wiped out of the apdata\local\temp...all i have is Wayload.esd on my desktop which I assume i copied to soon...it never changed from that name.

I copied the file to the Temp i made, which i see is not what we want. So i guess i run the media creation again.

 

[KYHI]

Copy - don't move to desktop.. Drag + CTRL to copy to desktop..

yes it gets renamed to decrypt after the - checking the download process

you don't have to hurry to snag it - as it will be there until the tool finishes..

But the PC has to be able to finish coping the file, before the tool finishes and deletes the file..

 

[sparhawk]

Whoa is me...now what:



KYHI I have an appointment untill after 6 pm. Let me know if you can be availabe to night or tomorrow would be fine

 

[sparhawk]

Looks like we have one more error?



Made directory c:\TEMP\x64

 

[sparhawk]

One of the error messages said something about an x64 folder.


So I made the directory c:\TEMP\x64 and copied the winplayload to both directories.


I have a copy on my desktop still. Also I changed the name to INSTALL.ESD.


Here are some of my errors:

 

[KYHI]

One of the error messages said something about an x64 folder.


So I made the directory c:\TEMP\x64 and copied the winplayload to both directories.


I have a copy on my desktop still. Also I changed the name to INSTALL.ESD.


Here are some of my errors:

View attachment 56110

typing error on your part

 

[KYHI]

Here you go - found the issue this morning.. I woke up to the same error you posted.. So I had to test and tweak to compensate..

View attachment 56114

Attached is the file from this morning - ISO creation Fixed

 

[KYHI]

Double click the New ISO to mount it and then browse to the sources folder - copy that install.wim to a new "base" folder
c:temp\base

View attachment 56117

Then run the commands from Image Prep.txt using your product key

Then refer back to post 13

And if all goes well - when you "reset windows 8.1" you should have a partitioned hard drive with clean windows 8.1 images applied

 

[KYHI]

The only other issue I for see is the use of which configfiles either BOIS or UEFI the system needs via how it was booted..

Once you boot the PC from recovery media if you go to advanced options - command prompt

Type> Wpeutil updatebootinfo

type> 'reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType'

*Note: you may need to remove quotes if you don't get the results of 0x1 or 0x2

if results =0x1 (your pc booted via bios and needs bios configfiles)
if results =0x2 (your pc booted via uefi and needs uefi configfiles)

 

[sparhawk]

Here you go - found the issue this morning.. I woke up to the same error you posted.. So I had to test and tweak to compensate..

View attachment 56114

Attached is the file from this morning - ISO creation Fixed

Where do i extract the WimISO.zip?

 

[sparhawk]

 

[MCPlayer18]

I wish I could help but I'm still learning. XD

 

[MCPlayer18]

Oh wait... This could be an exploit! There is a windows powershell exploit that has been unable to be fixed. For both windows 7 and 8. Try looking for an anti-exploit. I'm just saying it because you are using windows powershell.

 

[sparhawk]

oh wow! I am going remove every thing, temp directory and zip files all...do you think malwarebytes can find this exploit?

 

[sparhawk]

Why can't i delete these and where did they come from?

 

[KYHI]

Extract the new wimiso - and copy the files to c:\temp - same as before.....

copy the install.ESD that you renamed from winpayload.esd.decrypt to C:\temp

then run the

c:\temp\createwimiso c:\temp\install.esd

command..

Same as you did before - I know you know how to, you posted Pics of the program iso creation error..

You now have no need to be in AppData\temp folder.. And those are machine temp file - that is where your PC programs put them.. You just never seen them before and you will get more there as you use more programs..

 

[KYHI]

I wish I could help but I'm still learning. XD

Oh wait... This could be an exploit! There is a windows powershell exploit that has been unable to be fixed. For both windows 7 and 8. Try looking for an anti-exploit. I'm just saying it because you are using windows powershell.

and you have no clue what we are doing either, as he is using PS to run dos command to a file that does not exist..

 

[sparhawk]

Thanks Kyhi..the second time I used command prompt it almost finished. I don't think i did a screen shot.

I will abandoned usb drive...and just do the dvd install. We are gonna get this I know.

 

[KYHI]

the x64 error? yes I found the cause... and uploaded the fixed program files and a pic of the temp folder and iso creation

although the install.wim we needed was still in the temp\isofolder\sources\install.wim