IR5 - The Official Windows 7 Rearm Solution

@timesurfer,

I currently use Daz loader 1.7.7 to 1.79 and very happy because they are excellent Windows 7 loaders. I am equally impressed with your Infinite Rearm v2.3. Personally, your IR4 v2.3 in some aspect is more secured than bio-mod in light of IR4 now sets OS install date same as IR4 installed dates. I don't mind run IR4 every 150 days. With IR4 2.3, Is 30 day task for new 30 day trial history?

Windows 7 activation is not done yet as far as M$ is concerned. We may be laughing at M$ now, but I am concerned that new forthcoming W7 SP1 may possess some tricks in it that M$ may have the last laugh for people using loader. It is a games and in any games you win some and you lose some. I expect M$ may grab an upper hand sooner or later, if that happen, IR2.4 will come in handy while expert and brainy tech geeks at MDL work on circumvention of forthcoming new WAT from M$.

I want to test your IR4 2.3 in my old Dell laptop that has 2 hard drives (switch in and out). One small one that I can test IR4 2.3 in it. It has activated W7 Ultimate activated by Daz 1.79. DO I have to re-install W7 to use your IR4 v2.3? Can I uninstall Daz loader and run your IR4 v2.3? Is that the right way to go about it? Any guidance is appreciated.

 

Works perfectly!

 

Not sure how you would work around the problem I thought up today.

You reset the trial date in the registry but the Windows update history clearly shows all the dates which things were installed on. Anything that's prior to your said installation date will show WAT that the system's been modified as there would be a data mismatch. The same goes for installed programs etc.

 

Changing all dates would be impractical. The event log itself will show all the wrong doings in the system.

 

I was just caught unawares of the evil side of Run task if missed.

Here is what happened. I ran your program, declined the reboot because was updating my system. I had left the system idle for a while and suddenly I got "Your system has been rearmed successfully. Please restart your system for effects to take place.". Once the rearm is done there is no looking back.

Has any of you had a similar experience? Please share it here.

 

I didn't even run reset.bat, I was just idling in Windows and it ran automatically. This is just 15-20 minutes after clicking Install in IR4.

 

The task is running as it has been configured to run. Say when you click install now it sets the task at 14:30:00 every 30 days. After that the task scheduler will detect that the Rearm task needs to be run because the task has been missed and queues it. After 10 minutes (idle time) it will run the task and rearm.

I had noticed that the task being queued when I was testing the xml but ignored it each time by ending the task.

 

Yeah running twice will change the Task begin date to the current time.

 

I was able to recreate the above problem. Click Install and reboot. Open Task Scheduler and look at the Rearm task its status will be Queued. After 10 minutes of system idle it will rearm your system.

What I am trying to say here is you'll just lose your first rearm right after the reset.

One thing what I can do is change the task start time 30 days from the clicking install.

@ jverga

Can you share the Embedded default key with us, so we can add support for it.

 

I thought he had a different key because that version has been released recently. The only Embedded version on the key list is "ServerEmbeddedSolution". I just asked to compare the key with that one.

 

Reboot and don't do the RE cmd.