IORRT - The Official Office 2010 VL Rearm Solution

Yeah I'm just disappointed as OSPPRUN and those DLL functions did not help anything. The rearm count is useless since it doesn't detect locks and the License Uninstall is worthless as all it does is remove your ability to use a serial yet it retains the information inside tokens so reinstalling license would change nothing and uninstalling licenses gives no gain or purpose at all.

So now the only DLL thing useful is get SKUIDs and the time it would take to convert the output and write OSPPRUN to disk, pass input to it, close it and delete it makes the possible efficiency gains I envisioned with that function useless. and calling the DLL directly and all those annoyances aren't worth making EZ-Activator 2 seconds faster anyway.

 

If it runs the repair and successfully activates then yes. If he manually burnt the count down and activated KMS it won't.

To be 100% sure it will, have them run the License Repair in License Management then EZ-Activate it.

 

Right now I'm working on my uninstall thing.

I'm resorting to extreme measures now.

I confirm that a reinstall if office 2010 was bricked when uninstall is still locked 0 rearm notifications mode.

I'm watching the install with Total Uninstall, and I'm taking the capture WITH me purposely bricking and repairing office to see if it adds anything extra.

I am running on the principle that if no trace of Office can be found on the PC, then it cannot tell it was installed. My deepest concern is it modifies existing files that would always be on an OS (like a log entry I'd never find).

Backups are a different story as a reformat + clean install can have differences from a second format and reinstall. I gave up on the backup thing as I think you'd have to compare every single bit on the hard drive to see any difference that office could conceivably use.

Somehow playing with OSPPRUN and editing my installdate (was fine yesterday, I think it was me testing OSPPRUN and some other things) have rendered me unable to restore my MAK backup. Of course I have a backup image from acronis yesterday so I'll go back to that.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

No love for the AutoKMS? I think its very clean if not for the AV issues. I still have hope for KMS. I think it is improvable if we had an open source KMS Emulator as I have ideas that would minimize the failure rate and we could code it to be a bit less suspicious.

My worry about our rearm technique is that MS might find a way to beat it. The IR4 is harder to beat since it doesn't rely on restoring a backup. Things can change that break a backup. MS could simply store the date inside the backupped data and look at the startup date. They could set it up where they would forgive you for starting up your PC and the stored date being 6 months ago but somehow keep track of the dates with OSPPSVC or do some complicated stuff. All I know is it would be possible. If OSPPSVC updated some kind of encryption key or something.

And there is a bad thing if they do a WPA key like lockdown as we would not be able to import the data.

I don't think they'll go that route, as MS really cares about activators as grace won't pass because it is not activated. They care more about leaked VLK's and patches and surprisingly haven't even tried to defeat the loader in Win 7.

 

They could but I can't see how'd that benefit much. Even if AV's start attacking AutoRearm.exe, just add it to exclusions. It doesn't create any external files so there is no kill the keygen as it is written leading to activation failure.

I mean if they were that petty they'd flag the toolkit itself and I've not heard anyone say the toolkit exe or AutoKMS or rearm exe's are viruses that had any credibility (I'm pointing at those that go on torrents and scream virus at everything without DL'ing it just to cause trouble).

The KMS Server has so many things to alert AV.
1. It opens AND listens on a port
2. It is packed with some custom packer
3. It's written strange to make it harder to reverse.
4. It generates codes (think of all the keygens out there that AV's flag).
5. It is a server app doing strange network communications.
6. It's associated with mini-kms which I find that app is absolute garbage (one of the reasons I started the Office Toolkit - I hated mini-kms)
7. As an extension to #6 and others, it installed stuff that made it run 24/7 as a service (screams possible backdoor to some AV).

... and probably more things. I don't think AV's are hitting just because its a crack as I've never seen IR4, Daz Loader, or Office Toolkit get flagged and they are all very popular tools.

 

Well it's good you made IORRT and torrented it as I had AutoRearm 100% working before IORRT and nobody really knew about it as it hid behind the EZ-Activator which is what the toolkit got famous for. Also people being familiar with you and IR4 look at the rearm concept more favorably based on IR4 reputation.

 

Well I think unless we can reset count without a backup or disable nags on retail (which I convert to VL to make that irrelevant) then I'm not sure what the next step is.

and yeah since other than the loader there aren't many good solutions. Disabling stuff like DeathWAT/RemoveWAT I would not use unless it was the only way and KMS (which my AutoKMS can handle windows now) is not on all windows versions and windows can't be converted like office (plus you'd be losing features if you went to some of the KMS windows versions from ultimate).