"PA Bear" <> wrote in message
news:...
> You might tell us your Windows version, Ed.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Admin http://aumha.net
> DTS-L http://dts-l.org/
>
> Edward W. Thompson wrote:
>> I am unable to instrall updates and receive the error message "Setup
>> could
>> not verify integrity of the file Update.inf. Make sure the Cryptographic
>> service is running" Much info on this problem can be found by 'googling'
>> and I have worked through all that make sense, without solving the
>> problem.
>>
>> In particular I have worked through all solutions suggested at MS
>> KB822798 .
>> I have reregistered (regsvr32) 'dlls' and deleted/renamed 'catroot2'. I
>> have also registered/reregistered 'wups2.dll' and reinstalled the windows
>> installer using /wuforce. I have run the program 'dial-a-fix' and sfc
>> /scannow but the problem persists.
>>
>> This isn't the first time I have encountered this problem but previously
>> I
>> have managed to fix it, somehow, but there doesn't seem to be a single
>> reliable 'fix'.
>>
>> Any suggestions will be appreciated especially an insight in what causes
>> the
>> problem in the first place. If I knew why it happens at least I could
>> try
>> to avoid triggering it.
>>
>> What I haven't as yet tried is to do a 'system' restore. I have copies
>> of
>> the registry stretching back over ten days or more (ERUNT) and assume the
>> problem relates to the registry, is that correct?
Not sure why the WINXP version makes a difference but I am using WINXP Pro.
As a follow up despite following 'all' the advice I could find by 'Googling'
the original 'Cryptographic service' problem persisted. I have since
restored the registry (ERUNT) from several days back and then found that I
could now 'load' WINXP updates I had downloaded (i.e. "Setup could not
verify integrity of the file Update.inf. Make sure the Cryptographic
service is running" now fixed) but now I could not go 'online' or even
access the router (192.168.1.1). I reverted to the first registry and could
connect but the Cryptographic Service problem returned. I then tried
several other 'registrys' (registries?) all exhibited the same, that is I
could not connect despite the lights on the modem router all showing a
healthy connection (solid green lights) but the 'Cryptographic Service
problem was 'solved'. I tried 'ipconfig /release' and 'renew', in
desperation. Obviously they returned nothing as the machine was not
'talking' to the modem/router. Then, using a Registry without the
Cryptographic problem but with a 'connection' issue, ran the utility
'winsockxpfix.exe' which 'fixed' the connection issue and all now seems
'healthy' (until next time that is :-)).
It is a mystery to me why what were healthy 'registrys (registries :-)) when
backed up by ERUNT, seemed to be corrupt when restored, to the extent that
the communication between machine and modem/router was broken. I assume it
was a registry problem as I think that is what 'winsockxp.exe' 'fixes',
maybe there is more to it than that.
I post this litany as I hope it may be of help to others with a similar
problem. If anyone can enlighten me I would like to know the possible
causes for the 'cryptographic services' problem. It seems from this group
and from 'Google', it is common but I see no discourse on the possible
reason and means to prevent it. I suspect that in many cases while the
error message may point to the 'cryptographic service' being at fault, the
fault lies elsewhere otherwise, I assume, the fixes posted by Microsoft
would solve the problem. Perhaps I am being too trusting :-). It seems to
me, perhaps incorrectly, that the two problems, that is the Cryptographic
services problem and the not being able to 'connect' are separate.