Error 1935 when installing a new printer

#1
Hi,

I wonder if anyone can help.

I'm helping someone who has tried to install a new printer on his new HP PC (W7 64 Bit). The installation routine on the disk fails - no suprises there, given that half the stuff on retailers shelves don't have W7 disks yet. He calls for support from the retailer of the PC who point him to Kodak. The Kodak guy shows him where to download the W7 driver and then leaves him to it.

The installation routine hangs after a minute with Error 1935 Microsoft.VC80. Debug CRT, Type="win 32", publictokenkey=[didn't get this],version="8.0.50727.762" . Please refer to help and support for more information


Upon researching this I have found that error 1935 happens when a service is disabled or missing and sure enough if I go to services.msc I can see that 'Windows Modules Installer' is missing. I can also see that Trusted Installer has 'error 2' listed.

I have also tried sfc /scannnow which reports "Windows Resource Protection could not start the repair service"

I have run a quick Malwarebytes scan which reports that the memory and registry are clean.

Now, I am sure I can solve this with a full restore - but I was hoping that someone may have come across this before and knows what to do to get the modules installer back.


Thanks!
 


#2
You may need to update/repair the windows installer module:

Download details: Windows Installer 4.5

as well as net framwork:

Download details: Microsoft .NET Framework 4 (Web Installer)


~~~~~~~~~~

Also,

Fatal Error 'Error 1935. Fatal error during installation.' (MSI Error 1935) Displays During Software Installation

+

start > cmd > chkdsk /r,
start > cmd > sfc /scannow.
 


#3
Please refer to the following KB article for assistance on this error:
KB 946927 - An installation may fail with error 1935 when an .msi file tries to install many policy files on a computer that has the .NET Framework 2.0 installed
FIX: An installation may fail with error 1935 when an .msi file tries to install many policy files on a computer that has the .NET Framework 2.0 installed
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#4
If you are running a 64 bit OS you need a 64 bit driver. Has he tried letting Win 7 find a driver and has he clicked the update windows button while doing so?
 


#5
Solved

Hi All,

Thanks for the ideas. I found this solution to the problem:

1. Open a Command Prompt as Administrator
2. Type reg delete HKLM\SOFTWARE\Microsoft\SQMClient\Windows\DisabledSessions /va /f and press enter.

Win 7 Tip: Fix That MSI Installer Bug And Get Apps Running Again

Hope this helps anyone else who comes across it.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.