Jump to content

How to disable CTRL+ALT+DEL to log in to XP Mode?


Recommended Posts

This is really strange.  I was going to complain that I WANTED to disable CTRL+ALT+DEL to log in to XP Mode with Integrated Features on but COULD NOT get it to go away.  But now it's gone, I don't know why, and I cannot get it back!  (Yesterday-today was my first install of XP Mode and my first experience with virtualization, so I'm a noob.)


I tried four things to DISABLE CTRL ALT DEL, and they didn't work - CTRL ALT DEL was ALWAYS required with password.  And changing the XP Mode User Account to "no password required" just made it impossible to log in until I disabled Integrated Features and undid the change.


I tried the steps at these places - no luck:

http://support.microsoft.com/kb/308226   (the two manual steps)




So then I manually undid those steps.


BUT NOW CTR ALT DEL IS NOT REQUIRED!  How did that happen?  I UNdid the steps above, so it should be required now.  What's going on?


Is XP Mode always like this?

Link to comment
Share on other sites

Again please be clear about what you want to do.

In an other thread, you say you deleted an account (created by WSUS Offline). If this was one of TWO accounts, you are back to 1 (enabled) account and go straight to the desktop (if no password required). This may be an explanation.

Link to comment
Share on other sites

Ponch - Thanks again for info.


The WSUS link you gave me deleted its own temporary account when the XP updates were done - a superb app!  Many thanks.


But this business of log-ins on XP Mode is baffling. 


Right now, I'm back to all my XP Mode original settings, which had previously required CTRL ALT DEL with password (no matter what I did) -- and now don't, for no reason.


Well, that's why I'm experimenting, to find the potholes before I do anything important.

Edited by glnz
Link to comment
Share on other sites

FYI - your terminology is incorrect.


WSUS Offline doesn't "creat an account". It downloads all Fixes directly from MS and creates an Install, which you must have run accordingly. It *may* have deleted the Install Set - I can't offhand remember how it "works".


In addition, it *may* have overlayed some XP-Mode files/fixes. See this post (to further tie things together) -



Some "related" info (you probably have a CPU that supports Hyper-V/ "HT" on an Intel and on an AMD it's called "VT") -


Please note that the terminology gets real confusing. MS says this -

Intel VT, AMD-V, or VIA VT
(see this and the download links) -



In addition, the "standard" XP-Mode works like this during/after installation (scroll down) -



Baiscally, it uses RDP to interact with the Host OS. I don't have my Win7 PC hooked up (with XP-Mode installed) ATM, but I'd say off-hand that the "Auto-Logon" is enabled in the XP and you have no Password assigned? :unsure: If you go directly to the Dsktop, it means that you have that enabled (somehow). Probably the initial Installation (before Updates) caused CTRL-ALT-DEL (which you could have disabled?) to be the defualt but the Updates changed something (a registry key?) to allow for "Auto-Logon". Guaranteed if you add another User-ID in the XP-Mode VM that you'll have a "Welcome" Screen where you "pick" a User-ID.


Further info directly from MS -


(leads to...)


Everything you might want to know about Windows Virtual PC (not to be confused with Virtual PC 2004/2007) -



The theory behind XP-Mode is that you can literally run XP-only programs directly from Windows7 (actually "executes" on XP)) while XP-Mode is running. The intent was to make a stop-gap for those that had to use XP Programs that wouldn't run on Windows7. Just for fun, install a Third Part program on XP and see if you can run it from the Windows7.


I see you posted the exact same thing in your first post here -



HTH and have fun learning. :thumbup


P.S. - It's possible to extract the original VHD from the package if you want to start from scratch. That's how I discovered the "stunts" MS pulled (re - Integrated stuff). ;)

Link to comment
Share on other sites

submix - thanks so much for your continued interest!  Your links are very interesting to a newb tourist such as myself.


As a minor detail - and I do mean minor - wsusoffline's app does create a separate user account in at least certain cases, it was indeed running on my machine (it appears in the wsus log file after "user:" until I kept manually interrupting it and then again at the end when I finally let it finish), and in my case it did delete itself after the end of all the updates.


Just fyi - see these links, one of which is my own post:






And, yes, my Opti 7010 does support hardware virtualization.  I wanted to start my education in virtualization with XP Mode because it seemed easiest to download and learn how to use (and with an authorized copy of XP that passed the MS genuine validation step) and I knew it would try to use the HAV (I hope). 

(Another FYI - I was dismayed after I first got the Opti 7010 that the MS havdetection tool said that HAV was NOT available, but I eventually found out that my Avast Free antivirus was monopolizing use of HAV until I disabled "Enable hardware-assisted virtualization" in Avast, after which the MS havdetection tool said I DO have HAV available.)


Well, right now, with only a single user in my XP Mode, the default XPMuser, there is no longer any CTRL ALT DEL log in window even though I am back to the oririginal settings and the account DOES have a password.  Right now XP Mode boots to its desktop without a hitch.  OK, but strange I cannot control this.


I will check your links next weekend.  Many thanks, and feel free to post more.  I'm like a 10-year old with a science kit.

Edited by glnz
Link to comment
Share on other sites



"xpmuser" is the Default User account (google that). Since it uses RDP, I'm guessing that WSUS Offline needed to create a "special" account in order to run itself. I can't seem to find anything that specifically states which User Group that account initially goes under, but I'm betting that it's a Standard (restricted) User, set up in the Windows 7 Host to allow for RDP/XP-Mode and is *not* an "Administrator" (could be wrong). As I said, I don't have my Win7 box plugged in/running ATM so I can't check my theory. All indications are that it has something to do with User Priviledges (just a guess). You could check on that by going into "User Accounts" and see what Group it's under. Fair warning, I wouldn't mess with it (from what I've found) because it might "break" the RDP interface between Win7 and XP. Also, as I said, see if you can "add" a New User Account (only an Administrator *usually* has this ability).


Sorry, but I don't have time to "play" with mine so I can't give anything other than "what I know, what I can find, and what I can *assume*"

Link to comment
Share on other sites

FYI - your terminology is incorrect.


WSUS Offline doesn't "create an account". [....] I can't offhand remember how it "works".

Hummm... Why do you correct the OP several times if you can't remember how it works? :unsure:

WSUS Offline does create a temporary account which allows (optionally, it is) to complete the updates after needed reboot(s). It has nothing to do with XP-Mode nor with RDP nor with the Win7 host.

You can search for "temporary user" on this page.

Link to comment
Share on other sites

Thank you, Ponch for the further link.


Please be aware that Post#6 "semi" corrected my earlier post that you quoted. I now *completely" stand corrected.


It *may* be that WSUS automatically does that regardless of the User being an Admin or not by default. Otherwise, why in the heck would it do that (noting that Restricted Users *may* not have the Update ability)? There are exactly *two* references in that link that simply don't explain *why*. :unsure: Kind of "odd" that it may be necessary. I must be missing something.



It seems that it involves the Reboot (for some reason) and that *could* cause a problem if pysically interrupted.


Edit -

I also noticed that even though WSUS is downloading via the Official WSUS files, they *may* be incorrect as far as Superceded because I've compared their XP SP3 to UDC and found *many* to be unnecessary (including IE7). Indeed, if you install *all* Components in Add/Remove and use an Install Script along with the -X- UDC files you need reboot only *once*. Them go back and uninstall the "extra" if you really didn't need them. Take a look at the List compared to -X- List/ChangeLog. ;) IOW, WSUS Offline isn't that smart - same as/because MS does the same thing if you go to Windows Updates (download/install/rinse/reboot/repeat). Try it and find out as this subject has been broached before. :yes: Here's the explanation of why -X- doesn't download redundant/superceded Updates -


Bear in mind that I have "ignored" the Generated CAB files and used the Originals with the Home-Brew Script. The -only- ones (AFAICR) that required reboot was IE8 Fixes (after IE8 install) and MediaPlayer11 Fixes (after it was installed) because of the replacements in the Registry/FileSystem required for what is *really* an "Upgrade".

See this for a Functional Sample Script -


Note that it'll *still* install Fixes that you may include for Add/Remove Components that you haven't Optionally installed.


Not knocking WSUS Offline, just saying it has some "holes" in the process that can't be circumvented since MS is the one that screwed up.

Edited by submix8c
Link to comment
Share on other sites

As well as this going completely off topic,

I guess the author of WSUS Offline has concentrated his time on the ISO creation and other updates (Office and others) while -X- has taken his time to optimize the downloads/update process on XP post SP3 only. One does more, the other goes way faster. As long as they both work...

Edited by Ponch
Link to comment
Share on other sites

Ponch - Just so I understand:


A]   - X - is the same as http://xdot.tk/ ?


B]   I can use - X - (http://xdot.tk/) only to make an nLite slipstream XP install disk? Can I use - X - differently? That is, could I re-do the XP Mode installation using the initial XP Mode download from MS and then use - X - only to do the updates? How would I use - X - that way - what would I do?


C]   If I can do B], then will Belarc Advisor say I am missing lots of Hotfixes?


Thanks. Really - this is exactly what I want to learn to start because I will then learn to do this on VMWare or VirtualBox.

Edited by glnz
Link to comment
Share on other sites

@glnz, Since you have the means, time, interest and inclination to experiment, I hope you also try to update XP mode with SP4, if for no other reason than to confirm whether it works or not.  Of course, confirming the other methods will be useful as well.  It's always nice to have options, and some might prefer one method over the other.


Cheers and Regards

Link to comment
Share on other sites

@glnz -


A] Yes


B] Nope, sorry - see this



C] No, it will not


I started to "experiment" with "reassembling MS XP-Mode Install" from XP-Mode pre-install-files, but it's (well... read the post).

I guess that will just be a "project". You *could* use an OEM/Retail XP Pro, get the MS "internal" Key and insert the OEMBIOS files, but there's still the matter of certain VM-oriented files. I believe I have figured them out, but no time to test the theory. I just got an old PC reassembled and still have to hook up my Win7 PC again.


Theoretically, you could use -X- files and a script, but it *may* cause a "gltch" in that Optional Components (Add/Remove MS Components) won't be installed and -X- files include (I believe) some fixes for them. :unsure:


Stick with "Plan A" (WSUS) for the time. ;)  I'll revisit this after further testing (whatever...).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Create New...