What is the purpose for the unattend.xml in these images? I've made a few superaios with different versions of windows and they installed fine and had no integrity violations.
So I've started using install.esd recovery compression for win8.0 releases and I'm having a problem with a 97% bug. It will install until 97% then give an error. The weird thing is that it doesn't happen every time and sometimes even rebooting can get people past that bug. Short of simply using the win8.1 boot.wim and sources folder files, does anyone have any ideas which can potentionally solve this? Perhaps swapping some of the setup files from a win8.1 boot.wim index 2 image, or perhaps removing old dism packages from it and adding 8.1 winpe versions? Has anyone come across this issue yet?
Did you used /CheckIntegrity with .esd option?.... Windows 8 is capable of installing from .esd file... If you want to check you can replace boot.wim files from windows 8 ESD downloaded image, if you have one.... boot.wim is different in MSDN & ESD ISOs.....
Good idea about swapping the boot.wim files. The integrity is good. I've done checks during export and sfc scans after installs just to be sure since starting that method... I'll see if I can figure out how to get my hands on a boot.wim from an en-US esd version dvd for both x64 and x86... Lessee... some darn thing from microsoft lets you do that.... hmm how to find it...
murphy i checked & compared both images from boot.wim from MSDN & ESD iso & both are identical... yes no difference, its was just size difference between both wims 50KB... Problem must be different & swapping just files will not solve it....
Ahh... le' sigh. I wonder if swapping the setup.exe in the boot.wim index 2 for the one from the win8.1 boot wim... Hell with it... I think I'll revert to wim for 8.0 and just release a non-integrated version and make svf patches every month. I was reluctant to do that for xdelta back before I knew how easy it was to use SVF and how small the files were.
I am using esd with windows 8 & have no such problem faced.... i think you customized your image a lot like Sep2013 release & one of that customization is a problem... But SVF is very good idea as this will save people like me, having slow speed connection...
Yah it's a rare thing. Of like 10 indexes I tested, only one hit that 97% issue on win8. After rebooting and retrying the index installed correctly and had no integrity violations according to SFC The only things I do to my indexes are /add-package the kb msu files and copy over 3 small text/url files to windows\setup All I can think of is that somehow the size of the data is somehow causing an issue. Like perhaps running out of ram or something for the temporary extraction since the max compression equivalents are much larger. Perhaps the esd files use more ram.
I've found that when I try to do settings that aren't supported on the other images it stops my install. Settings I need in 2012R2 simply do not exist on W7, so to avoid collisions one can inject XMLs directly.
I will like know if as moderation this fórum can be, move this thread together with the threads fixed as well as the Ambidav thread about AIO and this posted by Murphy78.So it would be a complete tutorial on integration and construction AIO for windows 8.1,THANKS!
Murphy78 !!!!!! you rocks, excellent collection in TPB and special thanks for the win 8.1 AIO 7in1 En-Us.
I am trying to run the above script, but when it starts removing the apps I get everytime. Doing this under Windows 7 Ultimate SP1 (64 bit). Any idea on how to sort this out?
Hey does anyone know the correct order to integrate/update offline? 1) /Mount-Wim 2) /enable-feature 3) /Add-Package 4) /Add-Driver 5) /Set-ProductKey 6) /Cleanup-Image /StartComponentCleanup /ResetBase 7) /Commit-Wim 8) /Unmount-Wim Is the above order ok or should I "enable feature" after "add package"? Thanks
Ok, just went through steps 1-8 & "Clean-Image" step failed with error 0x800f0806, "The operation could not be completed due to pending operations".