yea that's why i don't use anymore apps like vlite or rtlite i just do it manually or using bat i made i never got to full stability with them :S
Might be nice on such cute little netbooks (i would never ever pay money for), but i refuse to install on a production machine.
yes i totally agree but removing comps with win toolkit is perfectly safe its just use internal tool to remove
Yah you have to be careful overclocking when exporting to esd... one tiny error and you will have problems. Still, I gotta give it to MS for multithreading the hell out of that. I'd much rather have a problem with running at 100% than a problem running at 20%
I've always been intrigued by "lite" builds. Were those made by you? where could I download the x64 one? Thanks!
@murphy78 i used /checkintegrity, should help catch those problem ? @slackeritguy yea 64bit will be up soon search lite8 at google/facebook
I'll have a look at the lite8 builds I've been busy developing a multi edition custom copy of Windows using an OEM pack of late
It will check most of them, but I recently ran into an issue where I took extra pre-cautions with /checkintegrity I ended up having the dreaded setup failed error at like 85% It doesn't happen on every index or even every time. I actually test like 5 indexes to make sure it doesn't happen once to make sure everything is ok. It seems to be fixed by defaulting the cpu settings and ram settings while integrating.. I also put a 10sec timeout just before each export just in case the NCQ needed a little time to catch up
its relate to decrypt the image the exporting from wim to esd went fine i guess decrypt don't have fail safe i had problems with exporting it to esd but wim wasn't good
I think you're onto something... I did initially try re-exporting everything to esd, and had same errors so ended up re-integrating. There's probably an error control somewhere in the setup that helps with WIM errors, but doesn't work with ESD errors that were inherited when exporting to ESD.
maybe try exporting the wim to new wim and then export to esd to make the allocation of wim as new when i lite or modified a wim i export it to make the wim "defrag" each wimfilter i use change the structure of it so i export it to rebulid the structure too sometime installation stopped with error cos didnt find same file but its was exist just because it was add after wim was done so it keep it on the end of the wim exporting fixed that
I already do that but there's no built-in hash check of files in a wim. You could literally make every file 0 file length text files and dism would not know the difference. The only way to go about fixing the issue is to re-integrate, re-export, and re-test everything, including post-install sfc /scannow check. I also do many install tests because the actual install seems to be where things get hung up, not the post-install. You can have all system files be 100% verified and setup can still fail at that 85%ish mark. It doesn't seem to happen on smaller files; rather large files with many similar indexes.
mb its ur hardware or wim bug sometimes i installing around 10 OSes a day on vmware ofc, nothing happened and i dont integrate i like live updating mb cos its pending and not really update just wait u to install the os and then complete i remember when i try use ICE on windows 7 long ago i used tweak to enable see the packages and when i tried to uninstall them its just a pending.xml and did nothing and it was offline image so live is work the best
Hey Lite8, there's gotta be something wrong with the .002 file for the Windows 8 X64 U1 build. Download gets interrupted every time: The rest of the files (all 5) downloaded perfectly from MEGA, so please check the .002 file. Thanks.
sorry for my ENG- Yes i want to add all available(officially) updates in windows update to my windows 8.1 msdn iso