MAVERICKS CHOICE

Ok after much testing found I had to mount the "Boot.wim" & change the Lang.ini , committed image & remade the iso working as expected now!

Recently been working with OEM Prox64. Though the default lang installed is en-GB & being so the install will halt until I answer the UI lang in setup. I have the relative passes in my xml & have installed en-US to the offline image & set this as default. eg. I changed the boot.wim from a good known us copy & adjusted the lang.ini. Setup still halts. I have read up on removing packages from offline images using Dism though the examples are limited. The installed .cab files extract once there put on the wim, therefore am not certain how it can be removed?? This is the MS example: Any advice suggestions are welcome.

I exported an original W8prox64 image from a wim & used a W8 test key as page one to install. Noticed that key is now invalid, probably why I require the pid.txt in Sources to have a partial UA install!

Hi Max If I remove the pid.txt from sources It gives the dreaded "cannot read product key" I have done many reinstalls using new VM's When I receive the above "cannot read product key" if I try to shift F10 to access either setuperr.log or setupact.log gives access denied! I do have "will wipe disk true" in the xml, same ans file I posted on page one of this thread.

Setupact.log attached. Setup still not behaving how it should my answer file? 1.Still asks to confirm W8Prox64!! (Only one image in wim)! 2. Asks to accept Eula!! 3. Confirm partition info!! All above info is included in xml!! However following confirmation of the above 3 items unattended install works exactly how it should as per my answer file!

Thanks Max understand I can only test in a VM atm & cannot for the life of me get the usb sorted!!! Either your doctored xml or my own xml will not work silently by itself. It works partially with the pid.txt in sources. I will be in touch with my MS digital provider to check or have my key replaced as I haven't had this problem before. I used to be able to install W7x64 no key & no problems previously!

Ive encountered the same problem & all appears to image/product key related. For instance there appears to many editions of Pro & you must use the correct key or windows won't setup! Even a generic key won't get you far either! I too have a valid "Pro" key but cannot produce a totally silent install yet?

No good Max, back to it's old habits!!

Ok just inserted that key into the edited xml. Will remake the iso now & test. So it will just be a matter of contacting my MS digital supplier for a replacement key later when Ive have this down pat?

Will do Max, also while on UA if I run my install, then reinstall windows won't activate on the same valid key? Is this caused by a previous install on a VM perhaps? Only tested this UA so far on VM's

Ok Max, I tried adding the ei.cfg info for Pro but no luck. With the xml in the Root & pid.txt & ei.cfg in Sources setup starts, asks me to select W8PROx64, (eg. only one available in image.) Then asks to accept Eula, then partition setup starts & runs. However totally silent there until desktop loads & complete! user account creates as xml. Generally the partition info & modify partition stuff is not?

Ok Max, getting my head around this throwing ei.cfg & pid.txt into the mix now has got me thinking. I insert my valid key to the pid file & setup with my xml ans file, windows asks to confirm "W8pro 64" & then "partition" & off it goes! No pop up re "product key" Yay!!!! Well then how to automate this from here?? Edit: Gotta say W8 appears to install abit quicker than previous versions!

Thanks Max for the xml, though it's still popping up! set the panther.cmd on the root of a usb & the virtual machine appears to enable the usb key & attaches it. When I shift F10 & check available drives using: wmic logicaldisk get caption that gives: Caption X: C: D: Tried to execute the panther.cmd from each drive & cannot find path!

Ok updated to latest Virtual Box ran my same build & still the dreaded "cannot read product key" pops up!! I omit the key info & install waits for the product key which I type in manually & installs good. So thinking it's not a key issue? Does windows 8 look @ the "product key" xml info differently to previous versions perhaps? See my xml attached with some info removed only. Running the 64 bit version if that makes any difference? Thanks for any suggestions in advance.

Thanks Max, just noticed the new version. Will update & report.

Max that's not very Bloody helpful!! I'm using Virtual Box, could you do me a favor & run your W8 Pro with Virtual Box & report back? Asking nicely

Generally run my test builds through Virtual Box, previously testing W8 ent edition with a modified W7 ans file & worked well. Recently swapped over to Pro if I manually install without ans file & type the product key no probs. If I specify in & use it in the ans file it gives the above "Windows cannot read the <Product Key> setting from the unattended answer file" Read all over the net re the VM Ware floppy boot problem, which is not selected in my Virtual Box. Anyone else experienced this or a resolution perhaps?

Hi Max, thanks for the update, all working very well here.

Thanks again Steven for keeping these updated.

That's fantastic Max, look forward to it!

Tried the following but no go! Msiexec /i nero.burningrom.msi /qn NERO.INCLUDED_KEY=XXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXX Windows6.0-KB942288-v2-x64.MSU /quiet vcredist_x64.exe /q Appears it won't install Neroburningrom on it's own?

Long time since I upgraded my Nero but can the current version be done a similar way? I have extracted the installer files to temp & really only require the "nero.burningrom.msi" to install. I have all the other files including the ISSetupPrerequisites folder. Any pointers always appreciated.

Great work guys I see were getting somewhere on this now!

That seems to be the problem every action for W8 images has to be with Admin Priv!!

Although off topic, Max are you thinking of adapting this for the current Dism in W8 perhaps? As I have used it on a W8 build & doesn't work correctly as previous! For instance the wim/info fails.