Hi guys, I tryied several times to implement a Key to my Unattended Edition and allways i got the same error: When i use the normal and original ISO it works, but after i use winreducer 8.1 and include the Key in it, it does not working! I based on this image: MICROSOFT.WINDOWS.8.1.RTM.X64-86.HEBREWN.DVD-WZT How can i solve this? Thanks! Rami
You just answered your own question matey. Don't "reduce" whatever it is that is blocking your key from being applied.
I tried both. With the normal and the original CD i have NO problems at all. I really dont think i mess with the whatsoever product key. By the way- you have a better way to easy customize an unattended windows 8.1 instead of winreducer 8.1? Thank you all!
Problem with those reducers: you don't know what it's doing exactly. Btw, what you're trying to reduce?
I really dont try to reduce. I just want to customize an unattended edition for my flavore. Ohh.. and include windows 8.1 updates in it.
seems to be a useless discussion here: you say that using the original iso, all works fine and after manipulating files you get problems .... guess what
To get this clear, FaiKee already asked, but got no answer; is the screenshot from Virtual Machine or a real PC?
You are customizing an already unattended edition of windows 8.1 and you have added windows 8.1 updates in it, So in autounattend.xml at the top see for the servicing packages section if there is disable/enabled packages entry then you need to change the windows 8.1 build string to match with the windows 8.1 updates one especially like the big update windows 8.1 Update 1 Packages. or else you can remove lines related to servicing packages part.
In VMware this error will occur if : - Machine setup is not "I shall install OS late", and/or - User does not remove the floppy(doesn't matter if there is a disk inside). But since OP said he tried both, so it's probably the reducer thing.
Was my thought likewise, know that behavior from that unattended floppy image in Quick Setup Mode of VMware .
Got it to work!! The problem was on my VMware. I intert the wrong serial in the VMware console and that cause me that error. Thank you guys!