Unable in install (mostly) anything 0x80070002

[cez81]

Win7 Pro 64.

I attempted to install Google Sketchup the other day and was given an error. I did a little research and tried a few potential fixes, but nothing worked (turning off startup services, registry edits, amount other things)

This is the entire error:
microsoft.VC80.ATL, type="win32", version="8.050727.6195", publicKeyToken="1fc8b3b9a1e18e3b",processArchitecture="x86"
HRESULT:0X0070002

Also, during this time period I did not renew Norton and instead decided to install AVG.
I ran into this similar error:

microsoft.VC90.ATL,version="9.0.30729.4148",publicKeyToken="1fc8b9a1e18e3b",processArchitecture="x86", type="win32"
HRESULT:0X0070002

Same HRESULT number.

Something in my reading said to try and install Visual C++ 2005, this came up with a nearly identical error as well. (though I am not sure if 2005 is compatible with Win7?)

I was able to successfully install MalwareBytes during this time, however.


What is wrong here? Is there anything I can try to fix this short of a complete reinstall of Windows?

 

[cluberti]

That error code is equal to "COR_E_FILENOTFOUND", so it would be interesting to see what a procmon log says while running the installer (with a verbose MSI log at the same time).

 

[cez81]

I installed procmon... but not sure how I should use it for my purposes.

Run procmon, attempt install of SketchUp, save procmon file, post?

What about the windows installer log? Where would the log be saved after I enable it?

Thanks.

 

[cluberti]

For the procmon piece, yes - open it, repro the issue (quickly), and save/post a log. As to the MSI logs, they're saved in %tmp% by default.

 

[cez81]

Here is the log file from procmon. It's all gibberish to me, so any insight that you or anyone can get from this is certainly appreciated!

I'll try to figure out the MSI logs tomorrow.



edit... file is too large, even when compressed... i'll need to host it later it seems...

 

[cluberti]

Yes, you'll want to simply zip up the .pml file that procmon creates and the MSI log file (make sure you take the procmon log AND the msi log AT THE SAME TIME), and host them somewhere.