Re: Error 0x800704DD and kb910341
- From: "Remi" <NOREMI@xxxxxx>
- Date: Tue, 27 Jan 2009 17:33:14 +0100
Hello and thank you for your help!
Apparently, that's what is causing the error message. Question is, how did
they get moved to Notify_disabled ?
No idea how Notify_disabled came in there...
You can open compare the keys in Notify_disabled to the keys from my XPThey are the same
Pro box and see if they're the same:
choosing Export. Save them to the Desktop as Notify_disabled.ok.
Next, open Notepad. Copy and paste ALL of the below into it making sureIf i understand correctly i merge SensLogn into \Notify\
....
Then click File > Save as > and set the " Save as type: " to All Files.
Name it SensLogn.reg
Now click Save.
..
Delete Notify_disabled now. You still have a backup of it on the Desktop,
just in case <w>
*Right* click SensLogn.reg and choose Merge.
but what happens with the other (x) folders in Notify_Disabled ??:
(x)-crypt32chain
(x)-cryptnet
(x)-cscdll
(x)-ScCertProp
(x)-Schedule
(x)-sclgntfy
-SensLogn
(x)-termserv
(x)-wlballoon
Do i see it correct saying; export Notify_Disabled to the desktop as
Notify_Disabled.reg and make a security-copy of it.
Open Notify_Disabled.reg with Notepad and change all \Notify_Disabled to
\Notify
Save changes
Rename Notify_Disabled.reg in Notify.reg
Delete Notify_Disabled (registry)
Merge Notify.reg
Restart and wonder :-))
Remi
.
- Follow-Ups:
- Re: Error 0x800704DD and kb910341
- From: MowGreen [MVP]
- Re: Error 0x800704DD and kb910341
- References:
- Error 0x800704DD and kb910341
- From: Remi
- Re: Error 0x800704DD and kb910341
- From: MowGreen [MVP]
- Error 0x800704DD and kb910341
- Prev by Date: svchost.exe 100% CPU when inserting MSDN disk
- Next by Date: WSUS 3 issue
- Previous by thread: Re: Error 0x800704DD and kb910341
- Next by thread: Re: Error 0x800704DD and kb910341
- Index(es):