Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Possible cause of 1935 error with HRESULT 0x80070002

Possible cause of 1935 error with HRESULT 0x80070002

  • Comments 68

I was helping investigate a .NET Framework installation failure last week that turned out to have an interesting root cause, so I wanted to pass along the information I learned.  The .NET Framework was failing with a 1935 error, and the HRESULT value was 0x80070002.  In general this HRESULT means "the system cannot find the file specified" - and since the .NET Framework is packaged up in a single self-extracting package, it is nearly impossible to get this particular HRESULT during setup.

One of the developers investigated a similar issue and found that this particular HRESULT can be caused by a certain type of adware running on the machine.  If you launch Task Manager and then look at the Processes tab, take a look for a process named wtoolsa.exe.  If this process is running, you will need to clean off this adware (for example by following the suggestions at this site).

One note - the machine that I looked at that was infected with this adware was pretty difficult to clean up.  It relaunched itself when I killed the process, it replaced entries in the Run and RunOnce keys when I deleted them.  I didn't get a chance to try all of the recommended steps in the article I linked to, but I'm guessing there are some more aggressive tactics you could take to rip it off your machine.

Hopefully this will help some of you solve installation issues for the .NET Framework and other products that fail with 1935 errors with HRESULT 0x80070002.

  • In general, 0x80070002 stands for HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND). This error is returned whenever an app tries to do a certain file-related operation, like opening a file, and the file is not there.

    The error can be caused by a variety of reasons:
    1) Another application deletes the file while our application tries to open this file
    2) Some driver in the file system stack intercepts a CreateFile/ReadFile etc and translates the error code to "file not found" etc.

  • One option would be to right-click the file in the file system, and change the options in the security tab to deny "read and execute". If you kill it, it cannot restart itself.
  • Unload Ad-Watch and install MSN 7.0 without any problem
  • As the last person stated, unload Lavasoft Ad-Watch (or similar detection software) before installation and everything should go smoothly.
  • This seems to be MSI installation software version to adware or ad removing software. The original post discusses actual adware. Other following posts discuss the adware removing programs.
    My situation revealed problems not with Ad-Aware (which was installed) nor adware, but with WebRoot Spy Sweeper software and a Microstation v8.05 MSI installation software created with InstallShield.
    Ad-Aware remained on the machine, and WebRoot Spy Sweeper softare was removed. Install occurred as normal.
  • hi why cant i download MSN beta with this error
  • Hi Kerry, have you tried all of the suggestions in this blog article from myself and others who have posted? I would suggest trying these first because there is a lot of different adware/spyware and also adware/spyware blocking software that can cause this error. Please let me know if you have already tried these and not had any luck.

  • I had to wipe clean my hard drive to get rid of this problem. It occurred after I ran Webroot Spy Sweeper a few times and uninstalling the program didn't work.
  • I got this error (1935 - Hresult 0x80070002)installing the Veritas BackupExec remote admin console. Disabling Webroot Spysweeper (2) services allows you to correctly install Veritas Backup Exec remote administration console.
  • Ever since I published my blog post describing 1935 errors in more detail, I have been contacted by customers...
  • None of these solutions worked.

    BUT! creating a new Windows account and installing whilst logged into that DID work.

    Now I need a cigarette.
  • I was contacted by a customer this week who could not install the .NET Framework 1.1 due to a 1935 error...
  • I was contacted by a customer this week who could not install the .NET Framework 1.1 due to a 1935 error...
    Deciphering specific HRESULT values

    HRESULT 0x80070002 and 0x80070003
    HRESULT 0x80070005...
  • You resolved my problem of installing Veritas Backup Exec 10.1 (10d) on a Windows Server 2003 Small Business Edition (SBE). After 2 failed installations with the same error code 1935 ... HRESULT: 0x80070002. All I had to to was stop the antispyware and the antivirus software.
    We get used to the same old scenery and forget easy steps like this.
Page 1 of 5 (68 items) 12345
Leave a Comment
  • Please add 8 and 8 and type the answer here:
  • Post