Hi... Can I ask you about software installation through audit and sysprep by your OEM Recovery Tools? It would be nice to know is it possible to install for example Eset Smart Security, codecs, Windows 7 Manager...?
I am on Main desktop (OOBE), and I cheked the recovery partition i don' t found the SWM image, and when i try to restore the computer It say "He don't found the recovery image" ? (Sory for my bad english) Jeyak
so i read your intructions but still can't understand how to use the tool ? help please email is [email protected]
AnarethoS I have been testing ur oem recovery software 1.3.11 in vmware along with win 7 dvd multi oem / branding and with ur software added to it....fails to activate now and doesnt even install the branding either.....I have a feelin it might be something with the making of the setupcomplete.cmd but not sure.....I havent pen pointed it yet. Just sharing the info I have came acrossed. Look forward to hearing ur input on this. Note: I used the lil app here at this forum to mod the vmware bios to dell and has failed all 4 times I have tried. Ur software works but does something to the oobe or setupcomplete not sure which. Without ur software added with modded vmware bios to dell it activates and installs correct branding with the win 7 multi oem / branding. You can reproduce this everytime. Maybe sysprep does something to break the win 7 multi oem / branding....dont know for sure. Have a good day.
Yep, but is not a definitive solution You already spend more time to do the image, and when your're with the real end-user, time is money
I agree with chryses i seem the same problem after restore.cmd completed recovery drive definitely hidden but i ask this question on last page why the recovery drive hidden in first place..?? Why recovery drive auto hidden after run restore.cmd....????
ok got some answers for oem activation failing with the use of this recovery partition tool.....if you go into audit mode and manully run the oobe.cmd and then run the activate.cmd manually the oem activation always fails......in vmware and also on real comps so this is a problem. Is there a way of forcing the oem activation while in audit mode or are we **** out of luck? lol Hopefully you and the creator of the oem activation can hookup and come up with a solution for this problem.....it is reproducable every time. Funny thing in vmware is when in audit mode it see's vmware and not the modded bios for vmware set as dell.....still see's vmware instead of dell. While in audit mode the oem activation fails but if not using audit mode it see's correct manufacture and activates and brands the machine weather vmware or real comp. Its audit mode that is the issue with oem activation failing to work. If I add windows loader by daz to the script for oem activation it works in audit mode.....strange.
Hi everyone. If I understand correcly, most of your problems are when you are using my tools with self-activating Windows disk. I suppose my tools damage the SetupComplete.cmd file already present on your disk. Before installing my tools, can you look if there is already a SetupComplete.cmd file and, if yes, give me it contents? Also, for those of you you still see the recovery partition after OOBE, can you do the following (on a fresh reinstall and during the firt time you are in OOBE) - Press SHIFT+F10 - Open DISKPART - List volume and give me the pritout Thanks.
its not the setupcomplete.cmd script that is the problem I found out.....it is goin into audit mode and tring to oem activate there.....if not in audit mode then oem activates perfect....I dont think it is ur tool but the oem activation method used in the multi oem folder that searchengine created. Yes it does create a existing setupcomplete.cmd but only to del script folder and delete itself after completion. Not much to it and ur software does write to the setupcomplete.cmd at the top add ur line of code. No problem there but it is the oem activation that I cant figure out. Hopefully searchengine will come online and read what I wrote and might have a workaround for those of us wanting to oem activate within audit mode. I really dont think it is ur software causing it but the limitation of audit mode itself. I have been testing since 5am this mornin and it is now 3:34 so time for a break. lol Confirmed it is the multi oem folder that searchengine created is the problem within audit mode.....sorry to bother you with this. Thanks for ur interest though. lol
I neved activated my Windows copy from Audit mode. Always done it in OOBE/Full install mode. The only computer I have activated during AUDIT mode was those with SLIC 2.1 bios. The activation was kept in that case. If you use DAZ loader or a similar methor to activate, you shoul not try to activate during the audit mode, but ratehr use the setupcomplete.cmd method to run the activator. In case of a legit key (retail, etc.) you will have to use ATM to backup/restore your activation or script it by hand in setupcomplete.cmd to replace the required DAT files by the correct one. I know there is a way to disable REARMING the computer in sysprep.xml. M$ documentation may help you there.
maybe i am not clear....when you use ur xml file to auto boot into audit mode to load drivers and and then u install ur tool it will then restart to make image and continue with install but some how it corrupts the multi oem activation and only loader will install because it doesnt see correct manufacture....see below.. As see above it should activate and install branding for Dell but doesnt.....only see's vmware and it is modded to dell. Uses loader instead for none of the manufactures show up if you enter into the audit mode using ur xml file. Hope this makes thing clear.....lol I need sleep. lol If I only add the oem folder to sources in win7 iso and not use ur software it will install correctly everytime but if I have to go into audit mode like your instruction say to and load drivers then use ur software it will corrupt the multi oem activation....why I dont know.
if you make a install windows 8 usb do you also put the auto AutoUnattend and the settings with it too ? and how does it start everything
Copy the AutoUnattend.XMl in the root of the drive. Copy manually the recovery Tools installation files to the computer prior launching the installation.
Well... I am now clueless. My XML file only create the partitions and force switching to audit mode, nothing more. Can you try the following? - Don't use AutoUnattend.Xml file - From Windows installation media, before clicking "Install Now", press SHIFT+F10 - From command prompt, create required partitions - Install Windows - Windows will boot in OOBE. Dont type anything and press CTRL+SHIFT+F3, this will reboot in Audit mode Does is works this way?