Guillaume

After a re-install with the only difference being the following components left in the installation, all works fine (before, I got DCOM error 10000 events as well): RPC Locator (Remote Procedure Call) Logon Notifications Still don't know exactly what Logon Notifications does, but my guess is definitely that the Remote Procedure Call (RPC) service was is the one responsible for the automatic starting of processes such as rdpclip. Thanks for the help.

- sorry, wrong topic

Easy there, you misunderstood me now! I just said I found it 'pretty crappy' that I didn't fix it yet. I checked Viper's site, and it doesn't state explicitly that rdpclip needs clipsrv (rdpclip is mentioned nowhere on the site), but from the description of clipsrv it does seem plausible (that's why I asked in my previous post). What I do know is that clipsrv (ClipBook) is not necessary for rdpclip to work: I currently just start it when I boot the system. Concerning memory usage: I saw that rdpclip uses only 2,480KB, while according to Viper the ClipBook service uses 1.3MB. BUT it's set to manual normally, so it won't run until needed (which presumably will be when I initiate an RDP session, in order to start rdpclip?). Last session.ini is up-to-date.

Does rdpclip.exe in any way relate to clipsrv.exe (which seems to be deleted when the Clipboard Viewer component is checked for removal)?

No I didn't get it solved, pretty crappy.

I'm sorry, but I'd like to give the topic a modest bump. Really interested in a possible solution.

That is no answer, please don't say anything if you don't have anything to contribute.

Whenever I initiate a remote desktop connection, Windows will not start rdpclip.exe on the host system, needed for sharing the clipboard. This is where rdpclip comes in (registry): [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Clip Redirector] "Name"="RDPClip" "Type"=dword:00000003 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\SysProcs] "rdpclip.exe"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd] "StartupPrograms"="rdpclip" See .INI attached. Can anyone be of assistance here? Athlon_2008_v2.5.ini

Power Management in general or to be able to use some tool they made for power management? If you messed up like me and removed this service aswell you can manually instal it even after XP is installed, you are going to need an XP disc wich has it on though: http://www.lazybit.com/index.php/2007/12/1..._service?blog=2 Needed to do this after I found out my HP printer drivers wouldn't install because that was missing... Huh? That is the Smart Card Service, not the UPS service. By the way, the Smart Card service is NOT needed for HP Software: just use these reg-files instead.

Yeah maybe I confused things and was not too clear in my previous post by saying that the ATI Hotkey Poller service messes up with winlogon. Actually, what I am seeing, and I can reproduce this, is that the issue arises when the ATI Hotkey Poller is disabled. Thus, if you have an ATI card and driver installed and disabled the ATI Hotkey Poller service this might be the cause. At least for me this was the explanation although it may have been something specific to my system as well. Ok, I think you understand what I mean, but just to be sure: as the ATi Hotkey Poller service is disabled, it can't do anything that causes a problem, right? So it's the process that tries to communicate with the ATi service that causes the problems, which is... Logon Notifications. This gets confirmed by deleting the registry key I mentioned, which instructs the Notifications process to communicate a logon/logoff instruction to the ATi service, which it can't reach when disabled, causing really strange problems in the Welcome dialog. Yep, I came across this problem once or twice, too. I just checked and you're right: I did enable the 'never expires' option for all my accounts, but only the one with a pass actually got this property after installation.

I wasn't referring to the IE stuff being related to the logon notifications, no. But do you have any proof/earlier speculations of these programs being part of the problem?

I don't get what you mean, could you please be more specific? Under the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify, the following keys are present. I don't think many of them are actually necessary and heard decreasing the number of the entries here could really improve logon/logoff speed: crypt32chain cryptnet cscdll dimsntfy Schedule sclgntfy SensLogn termsrv wlballoon nLite also enables you to remove the component "Logon Notifications", which - I think - would completely remove the problem. Nuhi, am I correct if I state that this component is involved the process described above? I just found out that I still DO have a problem with the cursor not showing up in the password dialog, but pressing CTRL-ALT-DEL twice always worked. This supposedly has more to do with some kind of problem in the Common Controls v6 library (latest version of comctl32.dll in Windows\WinSxS).

I don't think it's the ATi service, since that one is either disabled or removed in the systems affected. Thus, what remains might be a problem in the way Winlogon handles the fact that it should send logon/logoff etc. messages to a service that isn't available. I think nuhi had the same problem with an nVidia card, but he is obviously smart enough to have the nVidia service(s) disabled as well... Don't know whether nVidia puts a link to its service in the Winlogon key mentioned earlier, though. Maybe someone could disable as many services as possible that are listed under that key, such as Secondary Logon, Cryptographic Services etc. Maybe this'll cause the same problems, otherwise, it's merely the way the ATi service uses this key.

Check the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify for keys that lead to removed/non-existing or disabled services. In my case AtiExtEvent key caused all the trouble, not any of the file versions in the hotfixes.

I think I finally found the solution. Apparently Winlogon will do some funny s*** when there's an entry in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify that won't work out well. In my case - BUT this can be any other key that leads to a non-existing service - the "AtiExtEvent" key under the Notify key above was causing all the trouble: I don't even have any ATi service running anymore.

Her ya go... "Active Directory service" and "Local Security Settings" were kept both in Athlon v1.0 For "Group Policy Management Console" ditto. There's only ONE admin account, the other two are limited user accounts. However, on another PC, multiple admin accounts and some limited account gave exactly the same results (but SP2 + updates back then: that initiated this topic) Athlon_2008_v1.0.ini Athlon_2008_v2.0.ini

Experiencing exactly the same now on an SP3 installation. - Suddenly asks for password when user has no password. Users that have a password: password not accepted. OR - Password input dialog has no cursor => cannot type in OR - Pressing CTRL-ALT-DEL twice (for classic logon screen) doesn't even work OR - Win + L (fast user switch) doesn't respond

nuhi, forget the thing about the visual styles not being present in the 'Appearance' tab. That's just a stupid thing I didn't know: the .msstyles file has to have the exact same name as the directory it is in. If not, Windows will not list it in the drop-down list under 'Windows and buttons'. Example: \Windows\Resources\Themes\Luna Element\LE5.msstyles WON'T work \Windows\Resources\Themes\Luna Element\Luna Element.msstyles WILL work

Can I manually add the missing visual styles to the dropdown box under Display Settings - Appearance?

Using 4.5 beta 2 (downloaded today). Slipstreamed SP3 b5508 EN into SP2 source. No further updates/hotfixes. 1. Some kinda problem here, too. When loading an .INI created by nLite v1.4.1, the themes were displayed as being added, but I was unable to choose a default theme in nLite. Removing them caused an error message. After the themes were "re-added" and Windows was installed, no theme in the list that came after the one I chose as default in nLite was available in the dropdown list within Windows (although they were copied). 1a. A file called $$!!$$!!.~~~ is present in %WinDir%\Resources\Themes (it's actually the My Theme(nL).theme file). I must include the remark that I'm trying to overwrite the file My Theme (nL).theme with one in $OEM%\$$\Resources\Themes. 2. After installation, the workgroup was set to 'WORKGROUP', where it should've been 'GUILLAUME' as specified in nLite. [edit] That's odd, it doesn't work in nLite 1.4.1 with a SP2 source either. Is it not allowed to have the same ('Guillaume') for username, organization and/or workgroup? 3. Uniterruptable Power Supply tab is shown in Energy properties, even though the component is removed.

That's quite odd. What I encountered when installing either of the WMLite packs mentioned above: - In IE6 I get a blank object - In Firefox (latest) I get an error message that the codec could not be found - In Opera (9.50Alpha), the object 'crashes' After installing WMP11 and using the np-mswmp.dll, it works, (npdsplay.dll doesn't). In IE, it still doesn't work...

Hmm, should be possible, as a full install of WMP does work...

Any way to get WMLite working when all WMP components are removed? I tried (without success): - WMlite10 / WMLite11 @ ksphere.free.fr - WMLite 2.4.0 @ free-codecs.com - Windows Media Player Firefox Plugin (Port 25) Guillermo_2_.ini

I integrated Internet Explorer 7 in the installation. Anything that loads with WinLogon that could cause this behavior?

I didn't know about the admins logon limit, and I must say I'm not really sure whether there is such a limit at all. However, switching to a limited user account is also either impossible (a password is rejected) or it's there's no way to get a cursor to fill in the password. Furthermore, I can't go back to the user still logged in, either (cursor is nowhere to be found). The new problem with the loss of a cursor happened when I started applying passwords to some of the user accounts.