Installation on XPMode

[aker]

IMPORTANT EDIT AT BOTTOM

aker - First, a note of appreciation for the wsusoffline website - wonderful, and very considerate for showing the youtube instructions from EliTheComputerGuy!

Yesterday and today, Jan 31 - Feb 1 2015, I installed XP Mode in my Win 7 Pro 64-bit machine - my first ever time with any virtualization. So your method of downloading updates is great.

I also enabled the "automatic reboot and recall" option, my PC created the "WOUTempAdmin" account, and on the reboots it tried to log in. However, I saw a CTRL + ALT + DEL login screen that was blank, so I logged in with XPMuser (my account) and my password. Windows then told me that WOUTempAdmin was actually running and my login would turn it off and cause loss of data. I went ahead anyway and logged in as XPMuser. However, the wsusoffline app then runs in my user account screen and finds and installs more updates (a few times now). (At the start, your app installed a few initial updates as "WOUTempAdmin".

wsusoffline's app continues to run to check everything, and it is showing a few more updates. And after that Windows Update is also showing a few more.

When they both agree that I have exhausted all updates, what should I do about the "WOUTempAdmin" user account? May I simply delete it? And what is the best way to delete it anyway?

Finally, for the future, how do I set XP Mode to restart and AUTOMATICALLY log in to XPMuser without a password (at least for these updates)?

Thanks.

IMPORTANT EDIT --

Sorry, but I was wrong! I decided to restart and let the XP Mode window just sit at the blank CTRL + ALT + DEL login for 20 minutes. Why? Because I figured out that the preceding prompts that WOUTempAdmin was active meant that this app is so smart it was doing its thing IN THE BACKGROUND in its WOUTempAdmin user account and I was only interrupting.
Indeed! Your app has fully finished and now DELETED the WOUTempAdmin user account. Genius! Superb! Wow!

I guess the only thing you need is a WARNING that if the user selects the "automatic reboot and recall" option and the restarts show the blank CTRL + ALT + DEL login, then just LET IT SIT or GO OUT FOR A PIZZA because it's all happening in the background.
Now, personally, I would prefer to see what's happening, so maybe there should be some info how to LOG IN to the WOUTempAdmin user account and watch.

Many thanks!

[aker]

Looks like, that wsusou's AutoLogon conflicts with the "integration features" (I just know the German term; "Integrationsfeatures") of Virtual PC.
As far as I know, it works as it should with them disabled; could you check that?

[boco]

The XP Mode with Integration features essentially works over an RDP connection. RDP logins work differently than local logins so the WSUSOU features are affected by that.

Without the Integration components active it is just a classic Windows Virtual PC VM, then WSUSOU should work correctly.

[Cababs]

I also noticed this. however I noticed that Windows Virtual PC has restrictions, meaning that it only used one processor and could only handle up to 3.5GB of RAM.

personal I use Oracle Virtual Box for any virtualisation and have no problem with the auto restart and recall function of WOU when I set up a XP vm

[boco]

VirtualBox VMs usually use the local display and thus work. If you enable the RDP server and use the VMs headless you might get the same issues, though.