Windows Integration Guide - murphy78

A lot of people that have issues relating to booting have hardware issues.
If you are using a custom driver, you might try using the Windows default drivers.
If you are not using custom drivers, you might try loading win7 and updating some firmware on hard disks or motherboards through the manufacturer's website.
Just be very careful with the firmware stuff. It should only be done as a last resort and there's always a risk of failing if there's some sort of cabling or power issue.
Make sure not to overclock your system in any way when playing with firmware updates.

Edit: noticed that you mentioned switching language after installing this. Yah you cannot do that. MS apparently hasn't updated their language file downloads.
What happens when you download the language is that it checks for all of the localized file versions that are required and downloads them.
With Update1 since it's not released officially, they haven't filled their servers with the appropriate file.

What you can do is uninstall kb2919355, change the language, and then re-install it if you want.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You have to use the dism.exe from the updated 8.1 2014 update 1 to /apply-image the install.esd indexes.
You can then capture the directory you applied the image to as a wim file.

 

Well... You could at least get win8.1 and use the latest wzt leaked msu file to get the dism.
As for capturing the directory just look up the dism commandline options...
They're pretty straightforward, usually some argument followed by a colon, and then the passed value.
There's already an install.esd thread about capturability... I'm sorry I didn't bookmark it... just search for it.

 

I think you may be confusing esd files with sysprep/capture methods.
Win7 doesn't use esd files because there is no install.esd support in win7 setup.

abbodi1406 is onto something about using vhd files to capture images.
I find that these are the best way to make captures of sysprepped stuff since offline-only modes tend to set everything to pending status for online integration.
If you go through the online integration passes and then capture the result, sure it might have unique identifiers, but if you used a VM it wouldn't exactly be tied to your machine in any way.

The best way to make a vm capture IMO is to use vmware and create your own vhd file.
Here's a rough breakdown on how to do that:

1) open diskmgmt.msc and create a vhd file. (dynamically expanding or not, doesn't matter)
2) initialize that vhd with mbr partitioning (right click on it)
3) disconnect that vhd after initializing
4) create a new Virtual Machine in VMware workstation and instead of letting it create a vmdk disk system, point it at the existing .vhd file you just created.
5) Run setup but go into audit mode at the user creation screen by pressing ctrl-shift-f3
6) Finish setting up everything you wish to do (Windows updates, extra software like Office, VC redist stuff etc)
7) Run the sysprep generalize option with shutdown parameter
8) Re-Attach the .vhd disk file in diskmgmt.msc and go through and clean up the image before you capture (You can remove windows\softwaredistribution\download folder and users\administrator folder safely)
9) Make your additional modifications to your liking. (This is the part where you would actually minimize your image by chopping up your image and fixing registry settings and winsxs database stuff)
10) Capture the mounted disk by pointing your capture program at it. (If it's I:\ then just point gimagex v2.1.1, dism, or imagex; doesn't really matter for win7 - win8 is better to use dism)

After capturing to an install.wim file, you can simply cut/replace the existing one in a win7 image and re-iso it.
Just make sure your ei.cfg file matches your index if you replace it in a file that you didn't originally use to install on the vm.

example:

Code:

[EditionID]
Ultimate
[Channel]
Retail
[VL]
0

ei.cfg files are not the only way to bypass the initial index selection, but they can be useful; especially if pointed at a VL image such as Enterprise or Professional

Again, esd files are much different than sysprep/captures. Until you create one using recovery compression on a win8.x image, you won't really understand them.

 

Nope, it's strictly to reduce the size of the install media or push-button reset image