When the recovery console not the cmd prompt opens it will say what your local disk is. forget about the X for now. That's just how it looks in RE Here is test If you get same problem then it's not IR5 Also you still didn't say what OS, arch your using To make it more clear for you 1. IR5 find's your OS and local drive then it creates IR5.bat file and puts it in system/local drive 2. Then IR5 boots auto into RE and you run the bat file then it auto reboots into windows 3. In windows it installs default key for your OS 4. Task creation and nag elimination happens before restart into RE Here is the code simplified that resets rearms Code: reg load HKLM\MY_SYSTEM "%~dp0Windows\System32\config\system" reg delete HKLM\MY_SYSTEM\WPA /f reg unload HKLM\MY_SYSTEM If used you still have to enter default key when back into windows
I still get the same problem with the test file. My OS info: Microsoft Windows 7 Ultimate 64-bit 6.1.7601 Service Pack 1 Build 7601 Thanks
Tell us what other hacks you used. Perhaps try sfc /scannow and see if anything is corrupted Also what local disk did it say in Recovery console before you choose cmd prompt. Please try to keep up ok Thanks
I have just used your IR4 and yesterday I uninstalled it and today I installed SP1 and tryed to install IR5. Running the command you wrote now. I will check what the local disk is after the check.
Oh, nothing against you as an uploader! Just that since it involved editing the registry, then booting into the recovery environment, I was a bit unsure. Plus I don't have the recovery partition, since I installed Win7 on a previously partitioned HDD, so I thought that might cause issues as well. Glad it all worked out fine though, so thanks a lot. Also, I wonder why MS didn't patch this "hole" with SP1? Ok, so no need to reinstall, got it. Guess I'll only need to do that (reinstall IR5) after 180 days now.
I understand it is trippy to go into RE the first time please tell me your OS 32 or 64, local drive Letter C, D or E? We are only dealing with system partition with IR5 lol...I said in that post I linked to that you SHOULD reinstall but you'll notice you have to uninstall IR5 first. This is to ensure your task is in sync with rearms
Win7 Ultimate x64, system drive is C. Just to confirm, I used IR5 yesterday, and today I updated to SP1. My Windows is still in first 30-day trial period (29 days left now) thanks to IR5. I have deleted the task that IR5 created and will just rearm manually when required. So I guess uninstalling and reinstalling IR5 is not required right now? Also, when my 180 days are up, do I need to uninstall IR5 then before reinstalling, or can I simply install it again to reset the rearm count? Thanks, sorry if these are stupid questions...
Yes in your specific "manual" situation you don't have to reinstall cause there is no need to sync task with the 5 rearms 30 days 43200 min's The task is what I use to detect if IR5 is installed so no real need to uninstall but uninstalling is harmless. Basically in your case an uninstall will put activation nags back hence you'll get nagged but upon install nags will be eliminated lol...however with my program so far if you rearm with it, it reinstall task so if I was you I'd reinstall IR5. Uninstall it first...lol Then just leave and if need be manually rearm with IR5 MS is not looking for task and task is meant to assist you not be troublesome ...lol
I was planning to rearm manually from the command prompt using slmgr -rearm, so I deleted the task. I guess there's no point in uninstalling/reinstalling IR5, since the basic work of resetting the rearm count has been done successfully. I know that! What I was talking about was this registry key that stores the rearm count, and how easily it can be deleted to reset the count. I thought that surely in SP1 MS will block this method. Oh well, good for us they didn't.
They gave us 5 rearms...lol IR5 is not an threat to MS since it can't be intergrated thus profited upon That is one reason I developed IR5 Mostly it was in case other exploits get killed but Daz, KMS and HAL/Chew have not. Even still IR5 is a cool solution that I can't seem to stop using. After having done Trilogy I like it even more and 6 months is a long time between 3 min installs Yea if in your case you use cmd prompt to rearm then no task will get created but I'm thinking of doing error check that if task is not installed to just rearm without task creation
It should work. IR5 is suppose to use C:IR5 even if your local drive is otherwise...lol You could try F:IR5 but I don't think it will make difference Does IR5.bat get put into F drive? You can open Trilogy cmd file and delete the shutdown line so windows won't restart so you can look
Three ideas for IR5: 1. After uninstall rearm still works. That is fine. However when rearming the code also creates task as that's how we stay in sync regarding rearm time and IR5 30 day task creation. So I want to, if IR5 task not installed not allow task creation. This is a problem when going to install again and because if you rearmed task was also created hence you'd have to uninstall again just cause you rearmed. 2. When uninstalling IR5 it gives successful uninstall msg. If you uninstall again it gives "can't find file or something" as it also says IR5 is already installed. I'd like it to not say "can't find file or something" but just IR5 is already installed no matter how many times you use uninstall function. 3. I might give "Windows is restarting now" msg at end of install function These things are not necessary cause they've been this way with IR4 for a while but thought I'd do better error checking
Yep, that's why it's so great. Also, I was kinda forced to use this because on my system while Daz's loader works fine, it slows down startup a lot. +1, that's a good idea. P.S. All 3 ideas above are great.
The task one will apply to you so you can just click rearm which is cooler I think I have to do nested check I dunno
No the IR5.bat don't exist in F: but I got it working now by installing IR5 again and in RE moving the new IR5.bat file from E: (where I found it) to F: an execute it there! After the restart the window came up with the rearm status and so on showing that all was correctly. And when I checked the status with the Trilogy file it recognized that IR5 is installed! Thanks for the help timesurfer
See IR5 support is the strangest of all exploits. You figured it out yourself like everyone else has so far generally speaking Yea the task is installed pre-boot-into-RE or right when you click install as is the nag elimination. Those two things always install no matter what. What you've learned is that for some reason the code that works for most to place the IR5.bat into system drive didn't for you? Later