IORRT - The Official Office 2010 VL Rearm Solution

@timesurfer

I managed to brick office and reinstall clean but it wasn't easy.

The way I did it way to install Office 2010 using Total Uninstall and I didn't stop at it setup complete, what I did was when it installed (still watching the PC) I bricked it and repaired it (without toolkit so I didn't have .NET 3.5 on the PC). When it repaired it was in the locked notifications.

I then let Total Uninstall make a log of everything and it is a lot of stuff. Since some of these files are in important locations and I don't know if other apps like VS 2010 will use them and its so much, and can vary with office edition a little, I really can't make a script of it.


However, Office can't possibly look at every single thing at that list. If we can narrow down to deleting only what is needed it could be efficient

Should I post my Total Uninstall log and people start narrowing down things left behind?

EDIT: I'm gonna try my first idea as there is some file I found interesting.

 

I need to target the most obvious first.

My idea is this:Office 2010 creates some file in a Crypto folder and it looks suspicious to me. If it has connections to license data and is unique per OS, it may have to do with backups as well. This is speculation and my mind hoping a lot but it's targeting this kind of stuff that produces results.

I'm going to go through my list and see what remains after an unaided uninstall and see the most suspicious things.

I really don't think having things like .docx file assigned to MS Word on install of Office are the trigger. I should test if reinstall of Office without bricking goes clean without aiding the process.

 

Yeah I said that since I'm getting tired, I'll finish destroying the obvious targets that may be at fault for reinstall errors tomorrow.

The log I have tells me everything whether its harmless or not. I need to narrow it down and the sheer size of the reg stuff makes the reg stuff too much for individual testing.

I may downsize things to make testing easier by installing a single app, not Pro Plus suite as there would be less reg stuff.

 

I think it would be a bit too much an that rearm line in IR4 is one thing with no if's or loops. It may be possible but I get a headache just thinking on how to cram all that on one line.

 

You need to login to view this posts content.

 

I know ensuring everything there is gone means Office 2010 100% cleanly uninstalled.
I don't know and don't plan to go through it anymore. I just wanted to see if it was possible to cleanup enough to reinstall Office fresh. Since EZ-Activator can unbrick people should just use that on reinstall as its way simpler.

 

You need to login to view this posts content.

 

As I said if you nuke everything on that list assuming things don't change by OS/Office Product then it solves the problem.

But it's too time consuming and complicated to go through all that list so I just recommend using EZ-Activator upon reinstall. I posted that in case it would be of use or someone could go thorough it.

 

Yeah I'm too tired, frustated, busy and overwhelmed to even think about all that registry stuff.

As I said though a successful repair + activate by EZ-Activator solves the problem so this is more effort than its worth. I'd rather use EZ-Activator than reinstall office just to unbrick it.

 

Well barring KMS Keygen failure, the EZ-Activator always fixes it if it does the repair while bricked. If the user has manually burned their rearms, they can run license reapir then EZ-Activator.

So EZ-Activator can fix anything without reinstalling anything, but it has to successfully KMS Activate to do so and so many people get the AV issue.