HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: Incomplete Setup on login - How to delete it?
Windows Server 2003
1832059
Members
2989
Online
110034
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2008 09:18 AM
05-19-2008 09:18 AM
Incomplete Setup on login - How to delete it?
Greetings!
I have a W2K3 Server w/ SP2 and everytime anyone logins locally they immediately get a setup dialog screen. The setup dialog screen does not appear when a user logins remotely. The problem is that the setup requires the original setup files which do not exist and the setup can not complete wihout them. In addiion, the setup can not be aborted only cancelled. What I mean by aborted is that I can not get rid of it. When it is cancelled, the dialog will go away only to reappear at the next local login. How do I get rid of this? I believe the answer is in the registry but I can not locate the source of the setup in the registry.
Thank you for your attention and if you have an answer I would greatly appreciate you sharing that with me.
Thanks again,
Steve
I have a W2K3 Server w/ SP2 and everytime anyone logins locally they immediately get a setup dialog screen. The setup dialog screen does not appear when a user logins remotely. The problem is that the setup requires the original setup files which do not exist and the setup can not complete wihout them. In addiion, the setup can not be aborted only cancelled. What I mean by aborted is that I can not get rid of it. When it is cancelled, the dialog will go away only to reappear at the next local login. How do I get rid of this? I believe the answer is in the registry but I can not locate the source of the setup in the registry.
Thank you for your attention and if you have an answer I would greatly appreciate you sharing that with me.
Thanks again,
Steve
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2008 11:59 PM
05-21-2008 11:59 PM
Re: Incomplete Setup on login - How to delete it?
Hi Steve,
Since you believe the answer is in the registry, try this AUTORUNS tool:
http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
It will tell you which registry keys are being loaded at logon or at system startup.
This may be due to a mid-install reboot required by a non-TS aware application (just a guess).
Hope it helps.
Edgar.
Since you believe the answer is in the registry, try this AUTORUNS tool:
http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
It will tell you which registry keys are being loaded at logon or at system startup.
This may be due to a mid-install reboot required by a non-TS aware application (just a guess).
Hope it helps.
Edgar.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP