hi ther have been getting error 1935 .... when installing adobe reader,
windows update also hangs during the first update. at the same time as the
error i get a message saying "windows installer modules has stopped work and
was closed"

part of me says this may be DEP issue or something along these lines, i have
tryed using another admin user to no effect

i am using ultimate 64 bit
--
grapes

"Craig008" <(E-Mail Removed)> wrote in message
news:58E466D1-D875-43EB-BC5E-(E-Mail Removed)...
> hi ther have been getting error 1935 .... when installing adobe reader,
> windows update also hangs during the first update. at the same time as the
> error i get a message saying "windows installer modules has stopped work
> and
> was closed"
>
> part of me says this may be DEP issue or something along these lines, i
> have
> tryed using another admin user to no effect
>
> i am using ultimate 64 bit
> --
> grapes

Did you try right clicking on the icon and choosing Run As
administrator ?

Another thing to try is if you already have an Adobe reader on your system,
uninstall that one first then try the new version.

If those don't work, search the Adobe forums for the error.

On 1/26/2012, korneto posted:
> Craig008 wrote on 11/21/2007 10:09 ET :
>> hi ther have been getting error 1935 when installing adobe reader,
>> windows update also hangs during the first update. at the same time as the
>> error i get a message saying "windows installer modules has stopped work
>> and
>> was closed"
>>
>> part of me says this may be DEP issue or something along these lines, i have
>> tryed using another admin user to no effect
>>
>> i am using ultimate 64 bit
>> grapes
>>
> A computer with Microsoft .NET Framework installed may show error 1935. This
> generally occurs while the MSI files are trying to install various policy
> files
> on your computer during the setup operations.

> Following are the various ways you can implement to fix error 1935

> 1. Reinstall Microsoft .NET Framework
> 2. Perform a Full Virus Scan
> 3. Full Scan your Registry
> 4. Re-register Windows Installer
> 5. Check System Files for Corruption
> 6. Clean the System Junk
> Try this i am sure your problem solution is here,

The original post was on 11/21/2007. By now Craig008 has probably
switched to the Mac :-)

--
Gene E. Bloch (Stumbling Bloch)

korneto wrote over 4 years later:

> Craig008 wrote on 11/21/2007 10:09 ET :
<snipped Craig's over 4-year query>
>
> A computer with ...
<snipped the severely late reply>

Picture a skeleton humped over a monitor with cobwebs everywhere.
That's Craig waiting for your over 4 year-old reply.

Check timestamps of posts before replying to them, especially when using
a webnews-for-boobs interface (web forum) to Usenet.