Error 1935 during 3rd party installation on Windows 10 64bit

Hi,

Thank you for being part of Windows 10.

If you receive a 1935 error when you try to install software, the Windows file system transaction log has become corrupted.

a.    Open an Administrator command prompt. To do this, press Windows key + X keys together and choose Command Prompt(Admin).

b. Now type, fsutil resource setautoreset true C:\

c.    This assumes that C: is the drive in which Windows 10 is installed. If it is installed on another drive like D:, please change the drive letter appropriately.

d.    Restart the system and check the issue.

Do get back to us for any issues pertaining to Windows in the future. We will be happy to help.

Hi,

Thanks for replying.

I followed your steps by running cmd as admin. Executing the line you provided it said the operation was successful. I shut off the computer and turned it back on.

After trying the installer again the same issue exists.

I have had problems with this error 1935 on Windows 10 too, but only when I have done a clean install (ie, Windows Reset and wipe files). In such a scenario, with nothing else installed, it is hard to imagine the "Windows file system transaction log has become corrupted". I even redid the Windows reset just to be sure but still received the error. I am curious if you did a clean install too, or just an normal upgrade?

I only solved my problem by reverting to Windows 8.1 from backup.

Very interesting.

I too did a clean install after upgrading using the Windows Reset and Wipe files. That's good to know resetting it again for you did not work. Either there is an incompatibility in the installers with Windows 10 or Windows 10 is missing something Windows 8.1 had...

I contacted Microsoft Tech Support and they are escalating my issue because they couldn't fix it. I should be getting a call back from them. Unless someone else has a solution for Windows 10 I'll keep you posted on the outcome in my conversation with them.

Now that I've gotten all settled I'd hate to go back and set everything up again for one program :)

Thanks!

Hi,

Ok so I just got off the phone with Microsoft and at this point there is not a fix with regards to Windows 10 and this 1935 error since we have all done a clean install. 

I have been notified that their engineers will have to create a Windows Update with a patch to this issue for Windows 10. How long this will take and where it is in their priority queue, I have no idea.

As far as our end goes we just need to notify the manufacturer of the program we are using of the error, and they need to provide an updated build for Windows 10. I have already done this for my program but will be forwarding this information to them again. Hopefully this will work for your issues as well.

I guess now all that's left is to hope they can either get us the Windows Update quickly or provide an updated build of the programs we are using quickly!

I have the EXACT same problem as you do. Error 1935>rolling back action>Error 1603 when trying to install the iLok License manager.
 I believe I've tried everything, including reinstalling windows 10. All it took to find this post (after 1 billion of google searches) was to use bing.com... funny, eh?
 If you ever manage to fix your problem with the iLok License manager, please let me/us know. I'll make sure to do the same.

Hey Robin,

I actually did manage to fix the problem. I had a hunch to try Compatibility Mode for Windows 7 after installing some Windows Updates one day and it finally worked!

1.) Find the installer (in my case "License Support Win64.exe")

2.) Right click on the installer and select "Properties"

3.) At the top of the "Properties" window click on the "Compatibility" tab

4.) Under the "Compatibility mode" section check the box for "Run this program in compatibility mode for:"

5.) A drop down box should become active. It's probably set to "Windows 8" right now.

    Click it and change it to "Windows 7"

6.) Click "OK" at the bottom of the "Properties" window

Now try running the installer. I may have even ran it as Administrator (right click -> "Run as Administrator"), I don't remember.

But after doing this the installer went through and installed successfully.

Let me know if this works for you! Best of luck.