- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsThis question has been opened so I can contribute a solution to a problem I haven't found many references to.
A had a number of workstations running Windows XP Pro SP1 in a Windows Server 2003 domain. Although we had made no changes to the local workstations or domain Group Policy, a small number of machines exhibited a problem with Printers and Faxes. The print queue objects (icons) no longer appeared when a normal user account was logged in. It didn't matter if the queues were network printers or local devices like a PDF writer. Not only were the queues missing but the "Add a printer" link in the left column did nothing when clicked. Furthermore, the "Send a fax" link was missing. Windows applications could not print; Notepad presented an error message while PowerPoint would crash. The problem did not exhibit itself when logged in as an Administrator.
Our troubleshooting efforts included disabling domain Group Policies, removing the workstation from the domain, ensuring Local Policies were not set, applying all outstanding Windows Updates. One machine started working properly again when we applied the .NET 1.1 updates but the other machines still exhibited the problem regardless of the current level of Windows Updates.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ebrodeurPosted on 2006-03-14 at 10:25:12ID: 16186240
(This comment is being added to provide a solution to the question posed above.)
om/kb/3132 22/en-us.
Not wishing to reinstall Windows XP on the affected machines we opened a support ticket with Microsoft and found a probable cause and solution. We surmised that a Registry setting was changed, possibly a side effect of changing domain Group Policy or a Windows Update, which disabled the Printers and Faxes feature in the user interface (GUI). I mention the GUI specifically because we could still print to network queues from the Command Prompt. We could also change settings on a print queue through an application's Printer Settings menu.
We didn't attempt to locate the exact Registry key causing the problem (you have seen the Registry, right!?) but we used the following solution to fix the problem. Please see Microsoft KnowledgeBase article 313222, http://support.microsoft.c
We ran the SECEDIT tool as described in the KB article which restored the user's ability to see and print to queues in Printers and Faxes. SECEDIT, when used as described, will reset Windows XP's settings to those a new installation. According to the MS tech it does not change settings on currently installed software (Microsoft or third-party). If you have performed a lot of local customizations via the Registry or Local Policies you will need to re-apply them. If you're using domain Group Policy the policy(ies) will be applied when you login which should bring the system back to your intended level of customization.
We have not (yet) run into any problems since using SECEDIT. I surmise this solution may resolve other weirdness with Windows XP where something "worked yesterday and doesn't today." SECEDIT is something like using a mallet to drive a nail (aka: overkill) so use caution if the machine is mission-critical.