open cmd prompt as admin then type Code: reagentc /enable Then try again also tell me what other solutions you've used and what build you got? To find out what build open start button then type Code: dxdiag
Bleh, I just realized my Path environment variable was changed to some obscure path . I'm going to check to see if that changes anything, but I'm currently on Build 7600 Enterprise 64. I'm going to check out if that fixes many problems, but I've also tried after IR5 Chew7 and HAL7600 and MBR Regenerator* but they've all failed so far.
Some have got IR5 to work with cmd path change. Use the watfix by daz or mbr regenerator to fix OS then attempt IR5 install again. Rearm concept always works just automated install sometimes fails due to various unrelated reasons not due to IR5
I'm still getting a reagentc.exe Operation Failed: 2 error when installing IR5, I don't get any keyboard/configuration notification when I start windows, and I've already gone through about 4 restarts using MBR and WAT Fix. I'm starting to think that /boottore is probably the problem, since I can't seem to force next bootup to be in RE. If my recovery image isn't working there's probably gonna be big problems getting this to work ><.
Hello Guys. So i try the Trylogy (IR5) again after doing clean install. I'm using it on two machines, one is my laptop & others on desktop. The one in my laptop sems OK so far, but not the one on my desktop. It is a clean install then update to SP1. I'm not applying any other activation method yet, nor installed any other program besides the driver & utility comes from motherboard CD, so i'm pretty sure there's nothing wrong with the OS. However, it is have 2 Drive with 5 partitions and have 2 OS installed, each on different partitions. But after doing the execution on Win RE, it's give some error message then restart the PC (too fast to take a picture or write it) At first, i thought maybe it's because the bat file loaded into wrong drive, but after i'm copying the IR5.bat file via command prompt to the correct Windows Seven System drive, it still give the error message. Any clue to why this happen? Thanks Adedd : Windows 7 Ultimate SP1 (6.1, Build 7601)
Click F8 at boot go into RE and tell me what local drive it says in the repair - (recovery) console window that you normally choose cmd prompt in
Hello time, thanks for the quick reply Do you mean what the assign drive on Win 7 System drive after boot into Win RE? It's F: on recovery console, but C: on normal boot Or do you mean the message error after executing the bat file in RE? I cant tell you if this what you mean, just too fast to take a picture or read the message.
recovery console and uninstall then reinstall then enter F:IR5 You can remove the IR5.bat wherever it is before you reinstall
lol I'm not using boot mgt software right now Well, i still have plenty of time to think about other alternative method. 29 days + 4 rearm remaining. It just make me curious why this doesnt work on desktop, while it works well on my laptop despite using the very same OS install source code. And i think maybe you as the developer might found it's interesting and want to investigate it further. Just shoot me if you want me to try something else or need extra info. I don't mind testing your method on my machine, since i love this method and the idea not tampering OS core file.
Actually, what you are noticing between your laptop and your desktop is most likely due to your drive(s) and partitions. Unfortunately, we haven't been able to pin-point the cause/fix for this. The majority of the time, all is OK. It appears that the problem (incorrect location of the IR5 file) occurs when either a non-typical boot management system is used, or when a multi-partitioned drive is used. The reason your laptop works is that it most likely has less complicated partitioning going on.
Yes sir you are correct again. I think we can nail it but it might take time. Yes I'm considering rearm project when win 8 rtm comes out
Let's see what happens. It's not worth trying anything with Win 8 right now as it will probably change once it reaches RTM. I think we still have a little while to go though before RTM happens.
Yes dude I will wait And I don't want to do KMS activator so if default keys are easily findable for all builds like we have now with IR5. Really if win 8 rearm concept will work we will be able to delete the WPA key if MS has left that open otherwise win 7 works fine and I can't really imagine win 8 being better...lol Task will probably work Actually probably the beta's could be used if we just installed task to rearm if slmgr stuff is same as win 7 Also will the anti-nag code work
Yeah, i notice that.. So, if i can conclude. A simple copy file to the correct drive then execute it couldn't fix the problem, right? Looks like i'll have to find other solutions. Anyway, thanks for the great work and answer. Keep rocking guys