Rick Selby's Windows XP Error Messages

Outlook 2002 & 2003 Outlook & Outlook Express Import & Export Outlook Express Files Export Outlook Express to Windows Live Mail Hotmail More E-mail Problems

Microsoft Shortcut Key and Office Shortcut Keys Microsoft XP Shortcut Keys

Window Media Player Hyper Links & Shortcuts Printing Favorite Links

"In God" † Prayer Requests † Jesus Help Page † Tribute to Sept. 11, 2001
"Christian" Merchandise † "If You Were The Father"
"Colon-Liver Cancer, God, My Story"

Think Adoption, NOT Abortion
If this site helped you, please make a donation to:

Feeding families around the world…and the corner.

John 6:27 "Labour not for the meat which perisheth, but for that meat which endureth unto everlasting life, which the Son of man shall give unto you: for him hath God the Father sealed"

"Of the People, by the people, for the people."
Not any more in the USA.
Now it is Of the people, by the government, for the government, big corporations, and rich.

ITS TIME FOR THE PEOPLE TO TAKE BACK AMERICA,
VOTE THE POLITICIANS OUT AND PUT IN GOOD PEOPLE WHO
CAN'T BE BOUGHT BY THE BIG CORPORATIONS AND RICH.
Read More, Politicians Running Wild

Windows XP Error Messages

Site Visitors

To find a topic on this page, Click Edit on the Toolbar, Find (on this page), type in keyword

you will not be able to find drivers for your hardware at this time.

Vista drivers

This is another repeat of XP SP 2.

Three things to remember when you are working with computers.

First thing is "YOU CAN DO IT".
Second take your time, a little mistake can cause a big problem.
Third all answers are only a question away.

TABLE OF CONTENTS

If you are experiencing computer Problems such as slowness, strange icons appearing, tool bars appearing, home page changing, please use one of the following links to check for a virus or trojan.

Panda Virus Free Online Virus Scan
AVG Anti-virus Program (FREE)
- AVG is a great "FREE" program and I used to keep a link to the download but they keep changing it all the time and I can't keep this link up to date so Google "Download AVG Free" to get the download link. SORRY!

ALSO Check the

XP Error Codes Page

if you can't find it here.

XP Error Messages

MS-DOS or 16-bit Windows-based Program Errors

"16-bit MS-DOS Subsystem" error message when you run an MS-DOS or 16-Bit Windows program in Windows Server 2003 or Windows 2000 Server
Error message when you install or start an MS-DOS or 16-bit Windows-based program
Unable to Start Win 16 WOW Applications
Win16 subsystem was unable to enter protected mode, dosx.exe must be present in your path

Access Denied Errors

Windows Cannot Access The Specified Device, Path Or File
"Access Denied" or "Permission Denied" Scripting Error Messages If Automatic Configuration Customizes Zone Settings
"Access Denied" When Using MS-DOS Prompt to Move Files
"Access Denied" Error Message When You Try to Delete a File
Configure The Firewall To Allow Remote Assistance

Add/Remove Program Errors

An unexpected error occurred. Class not registered
res://appwiz.cpl/listbox.htc
Line:225 Line Numbers may differ
Object doesn't support this property or method res://appwiz.cpl/default.hta
Line: 75 Line Numbers may differ
Error Message When You Remove a Program Using the Add/Remove Programs Tool

CD/DVD

CD DRIVE/DVD DRIVE:/ not accessible - Incorrect Function

Control Console

"Snap-in Failed to Initialize" Error Message When You Open Microsoft Management Console

Data Execution Prevention

Data Execution Prevention
A Windows security feature has detected a problem and closed this program

"Data Execution Prevention" error message in Windows XP Service Pack 2

E-Mail

Entry Point Not Found Errors

Cannot Locate the Procedure Entry Point FreeAddrInfoW When You Run an Application on Windows XP
Runndll32.exe entry-point-not-found error on my Windows XP installation
Rundll32.exe Entry point not found' when you open My Computer Properties

Error Reporting

Disable Error Reporting

File Error Messages

Windows Cannot Access The Specified Device, Path Or File
Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
Cannot delete file: The filename you selected is invalid or too long
Your System Has No Paging File, or the Paging File Is Too Small
ATL.DLL Cannot Be Found
"Delayed Write Failed" Error Message When You Manage Files in Windows XP
"File Does Not Have a Program Associated with It" Error Message When You Use the Run Command to Browse to a Web Site
"No Preview Available" and "File Format Is Not Supported" Error Messages Occur When You Try to View Graphic Files
Error Message: Error 633 Modem Is Already in Use
Error Message "Error 633" When Starting Broadband Connection
Windows Could Not Start Because the C:\windows\system32\config\system File is Missing or Corrupt
Winnt_root\System32\Ntoskrnl.exe
Winnt_root\System32\Hal.dll missing or corrupt
Explorer Caused An Error In Kernel32.Dll
Cannot Find shell.dll
shlwapi.dll Error Messages

Firewall

Configure The Firewall To Allow Remote Assistance

IE Explorer

Internet Connections Errors

Installing Errors Listed Under Setup

Media Player Error Codes and Solutions

Media Codes

Microsoft Digital Image

Error 1606.Could not access network location INSTALLDIR
Out of disk space. Disk space required for installation exceeds available disk space. The selected drive does not have enough space available to install Microsoft Digital Image Library 9. Click the exit setup button, free up additional space on your disk drive, and then run setup again.
Out of disk space. Volume "INSTALLDIR" required space 1kb available space 0 kb. Free some disk space & retry
Error 1317 An error occurred while attempting to create the directory c:\documents and settings\all users\documents\my music

Misc.

Graphics

"No Preview Available" and "File Format Is Not Supported" Error Messages Occur When You Try to View Graphic Files

Paging Errors

Your System Has No Paging File, or the Paging File Is Too Small

Page Not Displayed Error

Password Errors

Please Type a Different Password" Error Message When You Change Your Password for a Second Time

Pop Ups

Printing Errors

Printing Error: The printer cannot be found.
Error Message When You Print from Internet Explorer: Printing Error: The Printer Cannot Be Found
url res://c:\windows\system32\shdoclc.dll/preview.dlg

Schedule Task Errors

0x80090016 or 0x8009000f When Trying to Schedule a Task

Script Error

Error Message for Line: number can vary An error has occurred in the script on this page

Security Messages

Setup Errors

Microsoft Digital Image

Error 1606.Could not access network location INSTALLDIR
Out of disk space. Disk space required for installation exceeds available disk space. The selected drive does not have enough space available to install Microsoft Digital Image Library 9. Click the exit setup button, free up additional space on your disk drive, and then run setup again.
Out of disk space. Volume "INSTALLDIR" required space 1kb available space 0 kb. Free some disk space & retry
Error 1317 An error occurred while attempting to create the directory c:\documents and settings\all users\documents\my music

Startup Errors

Shutdown Errors

SP 2 Errors

Stop Errors

System Restore

Nothing Happens When You Click on System Restore or Help

Task Manager

Task Manager Has Been Disabled by Your System Administrator

TCP/IP and Broadband Errors

The TCP/IP network transport is not installed

Upgrading from Win 95, Win 98 or ME

"NTLDR is missing" error message when you install or upgrade Windows XP over Windows 95, Windows 98, or Windows Millennium Edition

Window Update Errors

Windows Update Troubleshooting
- You Get the Following Error Message: marscore.dll not found
When You Try To Install An Update To Windows XP Service Pack 2 Or To Windows XP Tablet PC Edition 2005, You May Receive A "0x8007f0f4" Error
"Administrators Only" Error Message When You Attempt to Use the Windows Update Site"
"Windows Update Was Disabled by Your System Administrator" Error Message

Winsock2 Errors

"No Preview Available" and "File Format Is Not Supported" Error Messages Occur When You Try to View Graphic Files

Error Message

After you upgrade to Windows XP, you may not be able to view graphic files, such as .jpeg or .bmp files, after you download them from the Internet. For example, when you try to open and the view the images, you may experience one or more of the following behaviors:
- You receive the following error message when you try to view the images by using Windows Picture and Fax Viewer: No preview available
- You receive error messages similar to the following when you try to view the images by using other graphics viewing or editing programs:

Solution

To resolve this behavior, turn off the option to compress graphics in CompuServe or AOL, and then download the graphic files that you want. To do so:
- Start AOL or CompuServe.
- On the Settings menu or the Access menu (as appropriate), click Preferences.
- Click Internet Properties (WWW) or WWW (as appropriate).
- Click the Web Graphics tab, click Never compress graphics, and then click Apply.
- Click the General tab.
- Under Temporary Internet files, click Delete Files.
- Click OK if you are prompted to confirm the deletion.
- Click OK.

"Access Denied" or "Permission Denied" Scripting Error Messages If Automatic Configuration Customizes Zone Settings

Error Message

If you use Internet Explorer 5.5 or 6 with an automatic configuration (.ins) file that includes custom zone settings, you may receive
OR
scripting error messages while you browse some Web sites. If you remove zone customization from the automatic configuration file, the problem does not occur.

Workaround

To work around this issue, use group policies or use a separate .reg file to customize zone settings.

Error Messages When You Start Your Computer if Windows Program Files Are Missing or Damaged

Error Message

When you start your computer, you may receive an error message that is similar to the either of the following:
- Windows could not start because of an error in the software
- Load needed DLL's for Kernel

Solution

To resolve this behavior, start your computer from Windows installation CD-ROM , and then perform an in-place upgrade of Windows. For additional information about how to do so, click the following article numbers to view the articles in the Microsoft Knowledge Base:
- 315341 How to Perform an In-Place Upgrade (Reinstallation) of Windows XP
- 292175 How to Perform an In-Place Upgrade of Windows 2000
- If Setup does not recognize your current installation of Windows when you try to perform an in-place upgrade, you cannot use an in-place upgrade to repair your installation of Windows. In this situation, you may have to completely reinstall Windows on your computer.

Win XP: Error Messages When You Log On to the Computer

Error Messages

Configuration Utility - You do not have sufficient access rights. Administrative privileges are required.
Configuration Utility - The installation of the Network Agent driver has failed. Access is denied.
Configuration Utility - Network Agent was not ready, and could not be installed.
Configuration Utility - Unable to connect the Network Agent driver. Program will terminate.

Cause

This behavior may occur if any of the following conditions are true:
- The computer has Windows XP Professional installed.
- You have a Limited User account for the computer.
- The computer has a Linksys WDT11 Wireless PCI network adapter card installed.
- The Linksys Instant Wireless Configuration Utility is in the Windows Startup group.
Because you have a Limited User account, you do not have the correct permissions to change the computer's network configuration.

Solution

For primary support of the Linksys WDT11 Wireless PCI network adapter card or any other Linksys product, visit the following Linksys Web site:
To download an updated driver, dated 5/31/2002, visit the following Linksys Web site:

Workaround

To work around this issue, upgrade your user account to at least a Power User account. The permissions of a Power User account permit you to run the Instant Wireless Configuration Utility. Ask the administrator of your local computer to provide you the correct credentials. An administrator can add you to the local administrators or power users group to resolve this issue.

Error Message: Windows Could Not Start Because the C:\windows\system32\config\system File is Missing or Corrupt

Error Message

When you try to start Microsoft Windows XP, you may receive the following error message:
Additionally, Windows may not start.

Solution

To resolve this behavior, start the Windows XP Recovery Console, and then restore the C:\Windows\System32\Config\System file from the C:\Windows\Repair\System file.
To do this, follow these steps:
- Use the Windows XP startup disks or the Windows XP CD to restart your computer.
- When the Welcome to Setup screen appears, press R to select the To repair a Windows XP installation using Recovery Console, press R option.
- Type the number of the Windows installation that you want to access from the Recovery Console, and then press ENTER.
- Type the administrator password when you are prompted to do so, and then press ENTER.
- At the command prompt, type the following commands (press ENTER after each command):
  - CD C:\Windows\System32\Config
  - REN system system.old
  - COPY C:\Windows\Repair\system
- Remove the Windows XP startup disks or the Windows XP CD.
- To exit the Recovery Console and restart the computer, type exit, and then press ENTER.

Error Message "Access Denied" When Using MS-DOS Prompt to Move Files Symptoms

Error Message

"Access denied"

Solution

To resolve this issue, use either of the following methods to copy or move items for staging:
- Start Windows Explorer, and then click and drag the items to the CD-R or CD-RW drive.
  -or-
- Right-click the files, point to Send To, and then click Writable CD

Workaround

To work around this issue, use a command prompt to move the items manually to the CD staging area, which is located in the following folder:

Error Message "Access Denied" When Using MS-DOS Prompt to Move Files

Error Message

Error 633 - the modem (or other connecting device) is already in use or is not configured properly.

Solution

To resolve this behavior, you must disconnect the existing broadband connection to establish the new connection. You must only have one broadband connection that is active.

Error Message Occurs When You Use the Add Network Place Wizard

Error Message

The folder you entered does not appear to be valid. Please choose another

Solution

To resolve this issue, type the server and share name in the Location box in the following format:

Error Message: Printer Driver Was Not Installed; Operation Could Not Be Completed Symptoms

Error Message

When you click Finish in the Add Printer Wizard, you may receive the following error message:

Solution

To resolve this behavior, use one of the following printer drivers (the most preferred driver is listed first): "
- A Windows XP-based printer driver (shipped with Windows XP or from the printer manufacturer)"
- A Windows 2000-based printer driver "
- A Windows NT 4.0-based printer driver

"Access Denied" Error Message When You Try to Delete a File

Error Message

Cannot delete filename: Access is denied.

Solution

To resolve this behavior, ask the administrator to grant the necessary permissions.

Error Message: "File Does Not Have a Program Associated with It" Error Message When You Use the Run Command to Browse to a Web Site

Error Message

This file does not have a program associated with it for performing this action. Create an association in the Folder Options control panel.

Workaround

Method 1
- Start MSN Explorer, and then type the Web address of the Web site that you want to browse to in the Address bar.
Method 2
- Turn on access to Internet Explorer from the Start menu and desktop, and then use the Run command to browse to the Web site that you want. To do this, follow these steps:
  - Click Start
  - Click Control Panel.
  - Double-click Add or Remove Programs
  - Click Add/Remove Windows Components.
  - In the Components list, click to select the Internet Explorer check box
  - Click Next.
  - Click Finish.
  - Click Start button
  - Click Run.
  - In the Open box, type the Web address of the Web site that you want to browse to
  - Click OK.

Cannot Preview 3-D Screensaver, and Preview Screen Is Black or Displays an Error Message

Error Problem

When the display color setting is set to 24-bit color, you may not be able to preview any of the three-dimensional (3-D) screensavers. The preview screen may be black, or it may display the following error message:

Cause

This behavior occurs if the computer runs Windows XP and uses an Intel video adapter and the driver that is included with Windows XP Although previewing any 3-D screensaver is affected, the 3-D screensaver itself works if you click the preview button.

More Information

The preview of a 3-D screensaver works if you set the display color to either 16-bit or 32-bit color.
For information about how to contact Intel Corporation, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
- 65416 Hardware and Software Third-Party Vendor Contact List, A-K
- 60781 Hardware and Software Third-Party Vendor Contact List, L-P
- 60782 Hardware and Software Third-Party Vendor Contact List, Q-Z

Computer Hangs During Shutdown or Displays a "Cannot Find Enough Free Resources" Error Message

Problem

After you click Start, click Shut Down, and then click either Restart or Shut down in the Shut Down Windows dialog box, the computer may begin to shut down but then stop responding (hang). When this occurs, the computer stops at a blank screen. The mouse pointer is displayed, but you cannot move it. The computer does not respond either to mouse movements or to keyboard input.
If your floppy disk drive is not present in My Computer, the Standard Floppy Disk Controller device in Device Manager may display the following error status: This device cannot find enough free resources that it can use. (Code 12)
The following STOP error message may appear when you shut down from Safe mode:
- STOP 0x0000009F
  Driver_Power_State_Failure

Solution

http://www.paceap.com

Error Message When You Remove a Program Using the Add/Remove Programs Tool

Error Message

An error occurred while trying to remove Program_name. Uninstallation has been canceled

Solution

To remove a program from the Install/Uninstall list, use one of the following methods.
- Delete the appropriate key under the following registry key:

"USB Power Exceeded" Error Message When Connecting USB Devices

Problem

The hub does not have enough power available to operate the device driver name. Would you like assistance in solving this problem? If you click No, the device may not function properly.
In addition, the USB device mentioned in the error message does not work properly and the device listing (located in the System properties of the Device Manager properties window for the device) is displayed with the following error message:
A USB device has requested more power than the hub can provide. Windows cannot enable the device. Remove the device and restart your computer.

Cause

Solution

Workaround

To work around this issue, disconnect the affected device from the passive hub and connect it directly to the USB host controller's hub (in the back of the computer).

The TCP/IP network transport is not installed

Method 1
- This is basically what Microsoft has to say about this.
  - In XP, TCP/IP is "integrated" into the OS. You can't uninstall it and reinstall it which makes the process difficult.
  - Note: This I picked up from a forum in which the gentleman said he worked for McAfee.
    - "McAfee has a tendency to corrupt the TCP/IP stack or at least it did, I do not know if the issue has been resolved by McAfee or not. So that is why I suggest you uninstall McAfee before continuing on.
      
      If you have McAfee virus scan uninstall it. This is no easy task as it doesn't do a clean uninstall. You may need to contact Network Associates for the current manual uninstall process, I didn't need to go that far though."
- In XP go to Start
- Run
- Type in
- At the next prompt type
- You may need to reinstall the modem or whatever other program might have been giving you the error message.
Method 2
- LSP-Fix
  - This program will fix problems caused by uninstalling programs that change the winsock2 settings. This program will not fix all problems but is worth a try if Microsoft's command didn't work. This fix is for Windows XP
  - If you have Adware installed remove it and then reinstall it afterwards for there is a problem with this fix and Ad-Aware that causes Ad-Aware not to work properly afterwards.
  - Download the following fix and follow the instructions.
    - lspfix.zip - includes the program and documentation
  Here is an image of the program
Method 3
- Delete and restore from another clean and working machine with the same OS the Winsock and Winsock2 keys of the registry:
- To do this on another machine go to the Start button
- Click on Run
- Type in or copy and paste
- When the registry edit window opens click on Search
- Click on Find
- Copy or paste in the following keys in one at a time and do a search for them
  - HKEY_LOCAL_MACHINE\System\
    CurrentControlSet\Services\Winsock
  - HKEY_LOCAL_MACHINE\System\
    CurrentControlSet\Services\Winsock2
- Once it finds the key (key should be highlighted, if not highlight it) click on File
- Click on Export
- A new window will open asking for a saving location and name the file.
- Give each key you exported a name and save them to a floppy.
- Then take the floppy to the PC not working and insert the floppy and copy the two files to the desktop.
- Double click on each file.
- You will get a message click yes to it and then you will get another message telling you that the patch has been applied. Do this with both files.
- Then delete the files from the desktop and reboot.
Method 4
- Replace the winsock files (I would try this last)
- Click on Start
- Click on Run
- Type in sfc
- Click okay
- Click on "Extract one file from installation disk."
- In the box labeled "Specify the system file that you would like to restore," type WSOCK32.DLL.
- To the right of a box labeled "Restore From" is a BROWSE button -- click on it.
- Show it the path to the win installation files.
- Click OK and OK again.
- After it has finished extracting the file, reboot the computer.

STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME" Error Message When You Restart Your Computer or Upgrade to Windows XP

Error Message

You may receive the following error message, where aaaaaaaa, bbbbbbbb, cccccccc, and dddddddd are hexadecimal numbers that may vary: STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME
Note: If you receive this error message when you restart the computer for the first time during an upgrade to Windows XP, your original operating system still works correctly. In some cases, a message appears on the BIOS report screen that states that the wrong cable is in use, but you may not see this message on computers that have a fast startup time.

Cause

This behavior can occur if either of the following conditions is true:
- Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller, and the following conditions are true:
  - You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable.
  - The basic input/output system (BIOS) settings are configured to force the faster UDMA modes.
- The file system is damaged and cannot be mounted. Solution
- To resolve this behavior, use the appropriate method.
- UDMA Controller
  - If your computer uses a UDMA hard disk controller, use the following procedures:
    - Replace the 40-wire cable with an 80-wire UDMA cable.
    - In the BIOS settings for your computer, load the 'Fail-Safe' default settings, and then reactivate the most frequently used options such as USB Support.
- Damaged File System this is usually the problem, running chkdsk will slove it.
  - If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged.
  - If this is the case, restart the computer to the Recovery Console, and then use the
    command to repair the volume. After you repair the volume, check your hardware to isolate the cause of the file system damage.
  - To do this, use the following steps:
    - Start your computer with the Windows startup disks or with the Windows CD-ROM if your computer can start from the CD-ROM drive.
    - When the Welcome to Setup screen appears, press R to select the repair option.
    - If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.
    - Type the administrator password when you are prompted to do so.
    - Note: If no administrator password exists, press ENTER.
    - At the command prompt, on the drive where Windows is installed, type chkdsk /r and then press ENTER.
    - At the command prompt, type exit, and then press ENTER to restart your computer.
  - If this procedure does not work, repeat it and use the fixboot command instead of the chkdsk /r command used above.

"Administrators Only" Error Message When You Attempt to Use the Windows Update Site

Error Message

When you attempt to use the Windows Update site, you may receive an error message similar to the following:
- Administrators Only
  To install items from Windows Update, you must be logged on as an administrator or a member of the Administrators group. If your computer is connected to a network, network policy settings may also prevent you from completing this procedure…
You receive this message even though you are already logged on as an administrator or a member of the Administrators group.
This behavior may occur if are not logged on as an administrator, if you use a computer that is behind a firewall, or if you use a computer that connects to the Internet through a proxy server.
This behavior may also occur if there are incorrect restriction settings on certain registry keys or if the %Systemroot%\System32\Catroot2 folder is corrupted.

Solution

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue, follow these steps:
Important If you access the Internet through a local area network (LAN) that uses a proxy or firewall, contact your network administrator to make sure that the firewall or proxy-server is configured to allow you to use Windows Update.
Log on as an administrator or follow the instructions in the Windows Update error message to use the Run As command with an administrator account. Try to access the Windows Update Web site again.
If the problem is resolved, do not continue troubleshooting.
If the problem persists Continue.
Click Start
Click Run
In the Open box
Type regedit
Click OK
Locate and select the following registry key:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
  Windows\CurrentVersion\WindowsUpdate
On the Edit menu
Click Permissions
Click Add
Then type Everyone in the dialog box that appears.
Click Check Names
Click OK
Select Everyone in the Group or user names list.
Under Permissions for Everyone
Click to select the Full Control check box in the Allow column.
Note that the Read check box in the Allow column is now also selected.
Select each user, in turn, in the Group or user names list, and then verify that no check boxes are selected in the Deny column.
Click to clear any check boxes that are selected in the Deny column.
Click the Advanced button
Click to select the Replace permission entries on all child objects check box
Click OK
Click YES if you are prompted for confirmation
Click OK to close the dialog box
Try to access the Windows Update Web site again. If the problem is resolved, do not continue troubleshooting.
If the problem persists
Add the following sites to the proxy exception list in Internet Explorer
To do this, follow these steps:
In Internet Explorer
Click Tools and then click Internet Options
On the Connections tab, click the dial-up or virtual private network (VPN) connection that you use to connect to the Internet, and then click Settings
If you connect to the Internet through your local area network (LAN), click LAN Settings.
Under Proxy server
Click Advanced
In the Exceptions box, type
Click OK three times.
Try again to visit the Windows Update Web site.
If the problem is resolved, do not continue troubleshooting.
If the problem is not resolved, remove these proxy exceptions and continue troubleshooting.
Use proxy connections to enable HTTP 1.1
To do this, follow these steps:
In Internet Explorer
Click Tools
Click Internet Options
On the Advanced tab, under HTTP 1.1 settings
Click to select the Use HTTP 1.1 through proxy connections check box.
Click OK
Try again to visit the Windows Update Web site again. If the problem is resolved, do not continue troubleshooting.
If the problem persists continue
At the command prompt, type the following commands, pressing ENTER after each line:
Try to access the Windows Update Web site. If the problem is resolved, do not continue troubleshooting. If the problem persists Microsoft Does Not have a solution for this error on your PC

Delayed Write Failed" Error Message When You Manage Files in Windows XP

Error Message

When you save or move documents or during general file-management activities in windows XP, you may intermittently receive "delayed write failed" error messages.

Solution

To resolve this issue:
Make sure that your UDMA hard disk controller is using an 80-wire, 40-pin cable. For information about how to do so, view the documentation that is included with your computer, or contact your UDMA hard disk controller manufacturer. Test to determine if the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to the next step.
Warning
- Do not change your BIOS settings unless you are very familiar with all the effects of changing BIOS settings.
- Make sure that your BIOS settings are not configured to force faster UDMA modes. For information about how to do so, view the documentation that is included with your computer, or contact your computer manufacturer. Test to determine if the issue is resolved. If the issue is resolved, do not complete the remaining steps. If the issue is not resolved, go to the next step.
Turn off the "Enable write caching on the disk" feature:
Note: If you turn off the "Enable write caching on the disk" feature, your disk performance may decrease. Because of this, you may want to monitor system performance after you complete the following procedure.
- In Windows Explorer, right-click your hard-disk, and then click Properties
- Click the Hardware tab
- Click the hard disk, and then click Properties
- Click the Policies tab.
- Click to clear the Enable write caching on the disk check box, and then click OK two times
- Repeat the above steps for each hard disk that is installed in your computer

Error Message 0x80090016 or 0x8009000f When Trying to Schedule a Task

Error Message

The new task has been created, but may not run because the account information could not be set. The specific error is:
0x80090016: Keyset does not exist.
The new task has been created, but may not run because the account information could not be set. The specific error is: 0x8009000f: Object already exists.

Solution

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To resolve this issue:
- Step #1: Start the Protected Storage service by using either of the following methods:
  - Use the Compmgmt.msc snap-in.
  - Type the following command at a command prompt:
- Step #2 Note If the Crypto subsystem has become corrupted, you may have to back up the following subkey, then delete it, and then restart your computer:
- Step #3 HKEY_USERS\.Default\Software\Microsoft\
  Cryptography\Providers\Type 001
- Step #4: Test to determine if the issue is resolved. If the issue is resolved, skip the remaining steps. If the issue is not resolved, go to step 3.
- Step #5: Start your computer in Safe mode, and then log on as administrator.
- Step #6: Double-click My Computer, and then click Folder Options on the Tools menu.
- Step #7: On the View tab, click to select Show hidden files and folders, and then click OK.
- Step #8: Delete all of the files in the "C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18" folder.
- Step #9: Restart your computer, and then run the task.

Runndll32.exe entry-point-not-found error on my Windows XP installation

Symptom
- If you right-click My Computer and select Properties or if you launch System Restore from msconfig.exe, you receive error:
  - Rundll32.exe Entry point not found The procedure entry RemoteAssistancePrepareSystemRestore could not be located in the dynamic link library winsta.dll.
- The System Restore tab will be missing from the Control Panel System applet.
Resolution
- Reboot the computer into Safe Mode (press F8 when the boot menu appears and select the Safe Mode option).
- After Windows starts, open Windows Explorer.
- Use My Computer, or Windows Explorer, to find %WinDir%\INF\sr.inf file (e.g., C:\windows\inf)And right-click the file sr.inf and select Install from the context menu. You may have to search for sr.inf in the hidden files and folders. Right-click the file sr.inf and select Install from the context menu.
- Reboot the computer in Normal mode.
If the previous steps don't resolve the problem, try reinstalling the latest service pack.

Rundll32.exe Entry point not found' when you open My Computer Properties

Symptom
- If you right-click My Computer and select Properties or if you launch System Restore from msconfig.exe, you receive error:
  - Rundll32.exe Entry point not found The procedure entry RemoteAssistancePrepareSystemRestore could not be located in the dynamic link library winsta.dll.
- When you run Msconfig and press Launch System Restore, you receive:
- Restrui.exe Entry point not found.
  - The procedure entry RemoteAssistancePrepareSystemRestore could not be located in the dynamic link library winsta.dll.
Resolution
- Reboot the computer into Safe Mode (press F8 when the boot menu appears and select the Safe Mode option).
- After Windows starts, open Windows Explorer.
- Use My Computer, or Windows Explorer, to find %WinDir%\INF\sr.inf file (e.g., C:\windows\inf)And right-click the file sr.inf and select Install from the context menu. You may have to search for sr.inf in the hidden files and folders. Right-click the file sr.inf and select Install from the context menu.
- Reboot the computer in Normal mode.
NOTE: If these problems persist, use Safe Mode to reapply SP 1a or install the latest Windows XP service pack.

#1:Windows Could Not Start Because of a Computer Disk Hardware Configuration Problem

#2: Windows NT could not start because the following file is missing or corrupt

#3: Winnt_root\System32\Ntoskrnl.exe

#4:Winnt_root\System32\Hal.dll missing or corrupt

Solution

Try all the methods below, some work for some people and another method will work for another person but it seems there is nothing that works for all. IF the first 4 methods do not work try the Repair Install and see if it will correct the problem. If not most likely you will have to reformat.

A bad stick of memory has been known to cause this problem also but not to often so you might want to check your memory to be sure they are good.

Method 1
- To resolve this issue, start the computer from the Windows XP CD, start the Recovery Console, and then use the Bootcfg.exe tool to rebuild the Boot.ini file:
  - Configure the computer to start from the CD-ROM or DVD-ROM drive. For information about how to do this, see your computer documentation or contact your computer manufacturer.
  - Insert the Windows XP CD-ROM into your CD-ROM or DVD-ROM drive, and then restart your computer.
  - When you see the "Press any key to boot from CD" message, press a key to start your computer from the Windows XP CD-ROM.
  - When you see the "Welcome to Setup" message, press R to start the Recovery Console.
  - If you have a dual-boot or multiple-boot computer, select the installation that you have to use from the Recovery Console.
  - When you are prompted to do so, type the administrator password, and then press ENTER.
  - At the command prompt, type bootcfg /list, and then press ENTER.
    - The entries in your current Boot.ini file are displayed on the screen.
  - At the command prompt, type bootcfg /rebuild, and then press ENTER.
    - This command scans the hard disks of the computer for Windows XP, Microsoft Windows 2000, or Microsoft Windows NT installations, and then displays the results.
  - Follow the on-screen instructions to add the Windows installations to the Boot.ini file.

Method 2
- Edit the Boot.ini file to restore or correct the Default entry and to ensure that the other entries in the [Operating Systems] section of the Boot.ini file point to the appropriate directories.
- For additional information about how to edit the Boot.ini file, click the article number below to view the article in the Microsoft Knowledge Base:
Method 3
- Use the Bootcfg utility in the Recovery Console to correct the Boot.ini file:
  - Use the Windows XP CD-ROM to start your computer.
  - When you receive the message to press R to repair Windows by using the Recovery Console, press the R key.
  - Select the Windows installation that you want, and then type the administrator password when prompted.
  - Type bootcfg /rebuild, and then press ENTER.
  - When the Windows installation is located, the following instructions are displayed:
    - Add installation to boot list? (Yes/No/All)
    - Enter Load Identifier:
    - Enter OS Load options:
  - After you perform the preceding steps, restart the computer, and then select the first item on the boot menu. This should allow Windows XP to start normally.
  - After Windows XP has successfully loaded, the Boot.ini can be modified to remove the incorrect entry.
- For additional information about how to edit the Boot.ini file, click the article number below to view the article in the Microsoft Knowledge Base:
Method 4
- Start the computer by using your Windows XP CD-ROM.
- Press any key to boot from the CD.
- After the setup files are finished loading press R to repair using Recovery Console.
- When you are in the recovery console, select the installation to log on to (usually number 1)
- Press ENTER.
- Login to the Administrator account by typing the password for this account, and then press ENTER.
- At the recovery console command prompt, type the following command, and then press ENTER:
  - For Uni-Processor systems:
  - For Multi-Processor systems:
    CD-ROM is the drive letter of your CD-ROM drive, and drive is the drive letter of the hard disk on which windows is installed.
- If you receive a prompt to overwrite the file, press Y.
- Type exit, and press ENTER at the command prompt.
Method 5
- Start the computer by using the Recovery Console, and then run the
  - CHKDSK /rcommand.
- Note You do not have to include the /p switch in the Chkdsk command-line because the /rswitch causes the Chkdsk utility to locate bad sectors and recover readable information. This command implies the /p switch..
- Note If the Default value in the [Boot Loader] section of the Boot.ini file is missing, Windows XP displays a new entry, Windows (default), on the OS Loader (boot loader) menu, and then defaults to the new entry. The Windows (default) entry points to the following path to load Windows XP:
  - multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
Method 6
- This one will only work if you have a second computer with Win XP, SP 1 or later
- Removed hard drive from computer
- Next install the harddrive in the second computer that has XP installed
- Make sure you set it as the slave drive
- Boot up the system
- Open Windows Explorer
- Click Tools
- Click Folder Options
- Set it to Display Contents of System Folders
- Show Hidden Files and Folders
- Remove check from Hide Protected OS Files
- Click Start
- Click Search
- Open Advanced Search options and put a check in all that are listed in the Advanced section
- Search D:\ drive if is this is the letter for the slave drive (drive you are trying to repair) for boot.ini and open it with Notepad
- Edit the boot.ini file by remove the extra Operating System added with option 1
- Close and Save changes to Boot.ini
- Click Start
- Click Search
- Open Advanced Search options and put a check in all that are listed in the Advanced section
- Search D:\ for hal
- Hal.dll may not be found but it should be in the D:\Windows\Systems32 Folder
- If it is there delete it
- Open C:\WINDOWS\ServicePackFiles\i386 and copy the hal.dll file to the D:\Windows\System32 Folder
- If you want you can hide the files and folders that you set to "Show" at the beginning of these instructions.
- Replace the slave drive back into the first computer
- Reboot
- On reboot you may be asked to reinstall some drivers, let it reinstall those drivers

XP Repair

Boot the computer using the XP CD
When you see the "Welcome To Setup" screen the following options will appear
- This portion of the Setup program prepares Microsoft Windows XP to run on your computer:
- To setup Windows XP now, press ENTER.
- To repair a Windows XP installation using Recovery Console, press R.
- To quit Setup without installing Windows XP, press F3.
Press Enter to start the Windows Setup
Note: Do not choose "To repair a Windows XP installation using the Recovery Console, press R".
Accept the License Agreement and Windows will search for existing Windows installations
Select the XP installation you want to repair from the list and press R to start the repair
- If the option to Repair Install is NOT available and you continue with the install; you will delete
  - The Windows & Documents and Settings folders.
  - All Applications that place keys in the registry will need to be reinstalled
  - Don't believe this, Microsoft says if the options is there you will not lose these folders
    and settings, you will even if this option is available you WILL lose these.
  - Click here to Gain Ownership or Permissions on Files and Folders if a hard drive fails to save or move the data to another drive.
- You should exit setup if the repair option is not available.
- If Repair is not available, XP is usually not repairable and will require a Clean install.
- Try the link below if the repair option is not available.
- A workaround might be to reconfigure the boot.ini using Recovery Console.
  - Boot with XP CD or 6 floppy boot disk set
  - Press R to load the Recovery Console
  - Type
  - Press Enter
  - This should fix any boot.ini errors causing setup not to see the XP OS install
- Try the Repair install again
- "Reboot, this time using the immediate R option, and if the CD letter is say E: use the following commands and press Enter after each
  - copy E:\i386\ntldr C:\
  - copy E:\i386\ntdetect.com C:\
  - attrib -h -r -s C:\boot.ini del C:\boot.ini
  - BootCfg /Rebuild
    - This might result in a damaged windows reappearing; but gives another chance of getting at the repair"
- Setup will begin
- Note: Do not reboot
- Do not press any key to boot from CD when the message appears
- Setup will install, but your applications and settings will remain intact
- If you get files not found during the copying stage check the CD to be sure it is not damaged or is not dirty.
- If the problem persists continue with the install by closing all the files not found message windows until setup finishes
- Then once you have windows installed run SFC /SCAN NOW to replace damaged or missing files
- Reapply updates or service packs applied since initial Windows XP installation. Please note that a Repair Install from the Original install XP CD will remove SP 1/SP 2 and service packs will need to be reapplied

Cannot Locate the Procedure Entry Point FreeAddrInfoW When You Run an Application on Windows XP

Note:

Microsoft Visual C++ .NET (2002) supports both the managed code model that is provided by the Microsoft .NET Framework and the unmanaged native Microsoft Windows code model. The information in this article applies only to unmanaged Visual C++ code.
This is a known bug that Microsoft knows about.

Error Message

The procedure entry point FreeAddrInfoW could not be located in the dynamic link library WS2_32.dll.

Probable Solution

Reduce the Behavior

You can try the following if you understand it or you can do a search for the file WS2_32.dll and download a new one.
If neither work for you then about all you can do is a "Repair Install"
- Start Visual Studio .NET 2003.
- On the File menu
- Point to New
- Click Project.
- Click Visual C++ Projects under Project Types
- Click Win32 Console Project under Templates.
- In the Name text box, type Sample and then click OK.
- In the Win32 Application Wizard dialog box, click to select the ATL and the Add Support for check boxes under Application Settings, and then click Finish.
- In the Sample.cpp file, replace the existing default code with the following
- In Solution Explorer, right-click the project node, and then click Properties.
- In the project Property Pages dialog box, click General under Configuration Properties in the left pane. In the right pane, set the Character Set property to Use Unicode Character Set. Click OK.
- On the Build menu, click Build Solution to build the application. You may notice that there are no compilation or linking errors during the build.
- On the Debug menu, click Start Without Debugging. You may notice that you receive the error message that is described in the "Symptoms" section.
- In Microsoft Windows XP and Microsoft Windows Server .NET, new Windows Sockets functions are added to the Windows Socket API. GetAddrInfo and FreeAddrInfo are the two new Windows Sockets functions that are added for dealing with both Internet Protocol version 6 (IPv6) and Internet Protocol version 4 (IPv4) addresses. The Active Template Library (ATL) 7.1 CSocketAddr class uses these new Windows Socket functions to provide support for IPv6. Other ATL and Microsoft Foundation Classes (MFC) classes also use the CSocketAddr class to provide IPv6 support. For example, the CAsyncSocket class (MFC class) and the CSMTPConnection class (ATL Class) use the CSocketAddr class.
- The problem that is described in this article occurs in any Unicode-enabled application that uses the FreeAddrInfo Windows Socket function on a computer that is running Windows XP Because the ATL CSocketAddr class uses the FreeAddrInfo function, the same problem also occurs in ATL 7.1. Any class in ATL 7.1 and MFC 7.1 that uses the CSocketAddr class to enable IPv6 support reflects this behavior. For example, the CAsyncSocket class (MFC class) and the CSMTPConnection class (ATL class) use the CSocketAddr class.
- ATL server classes such as CAtlHttpClient (that provides HTTP client support) and CSoapSocketClientT (that provides XML Web services client support) use the ZEvtSyncSocket class, and display the same error. This behavior occurs because the ZEvtSyncSocket internal class uses the CSocketAddr class in its implementation.
References
- For additional information about the changes that have been made to ATL, see the following Microsoft Developer Network (MSDN) Web site: C++ Libraries
- For additional information about the new Windows Socket functions that have been added to the Windows Socket API, see the following MSDN Web site: What's New for Windows Sockets

Error Message for Line: this number can vary

An error has occurred in the script on this page.

Line 1344
Char. 1
Error unspecified error.
Code: 0

Url res://c:\windows\system32\shdoclc.dll/preview.dlg

Do you want to continue running scripts on this page?

Yes / No

Solution

From a Win 2000 machine export these files from the registry and import on the machine with the print problem/script error. These work on both 2000 and Win XP
Windows Registry Editor Version 5.00
- [HKEY_CLASSES_ROOT\CLSID\{00000320-0000-0000-C000- 000000000046}]
  @="PSFactoryBuffer"
- [HKEY_CLASSES_ROOT\CLSID\{00000320-0000-0000-C000- 000000000046}\
  InprocServer32]
  @="C:\\WINNT\\system32\\ole32.dll"
  "ThreadingModel"="Both"
- [HKEY_CLASSES_ROOT\Interface\{0C733A30-2A1C-11CE-ADE5- 00AA0044773D}]
  @="ISequentialStream"
- [HKEY_CLASSES_ROOT\Interface\{0C733A30-2A1C-11CE-ADE5- 00AA0044773D}\
  NumMethods]
  @="5"
- [HKEY_CLASSES_ROOT\Interface\{0C733A30-2A1C-11CE-ADE5- 00AA0044773D}\ProxyStubClsid32] @="{00000320-0000-0000-C000-000000000046}"
- [HKEY_CLASSES_ROOT\Interface\{0000000c-0000-0000-C000- 000000000046}]
  @="IStream"
- [HKEY_CLASSES_ROOT\Interface\{0000000c-0000-0000-C000- 000000000046}\
  NumMethods]@="14"
- [HKEY_CLASSES_ROOT\Interface\{0000000c-0000-0000-C000- 000000000046}\
  ProxyStubClsid32]@="{00000320-0000-0000-C000-000000000046}"

Explorer Caused An Error In Kernel32.Dll

Fix #1
- Renamed the hidden folder in windows named "Applog" to Applogold
Fix #2
- Go to Add/Remove Programs
- Highlight Internet Explorer and choose Remove
- Choose the Repair option

Cannot Find shell.dll

Spyware removal programs sometimes delete or quarantine this file.
Click Start
Click Search
Click All files and folders
In the All or part of the file name box, type in
In the Look in list, click My Computer
Click Search
When or if you find it copy and paste it into C:\WINNT\System32 directory
If you cannot find it do a search on Google and download a new copy of it making sure the version number is for the version of windows you are running.

Error message when you install or start an MS-DOS or 16-bit Windows-based program

Error Messages

If you try to start or install an MS-DOS-based or a 16-bit Windows-based program on your Windows XP-based computer, you may receive an error message that is similar to one of the following:
Although you may be prompted to quit the program or ignore the error message, either selection makes the program quit

Cause

This issue may occur if one or more of the following files are missing or damaged: In XP %systemroot% is winnt directory
- Config.nt
- Autoexec.nt
- Command.com

Solution

Insert the CD into the CD drive or DVD drive
Click Start
Click Run
In the Open box type
Click OK
Type the following commands, and press Enter after each command In the commands below winnt is the directory for XP, if your system is not XP then expand them to your %systemroot% directory
- expand D:\i386\config.nt_ winnt\system32\config.nt
- expand D:\i386\autoexec.nt_ winnt\system32\autoexec.nt
- expand D:\i386\command.co_ winnt\system32\command.com
- Exit
Start or install the program
If the issue is resolved, do not complete the remaining steps
If the issue is not resolved, go to the next step.
Note: The Command.com file is not edited or created in this in the following process. Because of this, you may have to expand it from your Windows XP CD-ROM.
Start Notepad
In Notepad type the following entries:
On the File menu, click Save As
In the File Name box type
Click Save
Close the Config.nt file.
On the File menu, click New
In the new blank document, type the following entries:
On the File menu, click Save As
In the File Name box type
Click Save
Close the Autoexec.nt file. Start Windows Explorer
Locate the Config.nt file, right-click the Config.nt file
Click Copy
Right-click the %SYSTEMROOT%\System32 folder
Click Paste
Locate the Autoexec.nt file, right-click the Autoexec.nt file
Click Copy
Right-click the %SYSTEMROOT%\System32 folder
Click Paste
Locate the Command.com file, right-click the expanded Command.com file
Click Copy
Right-click the %SYSTEMROOT%\System32 folder
Click Paste
Restart your computer

"16-bit MS-DOS Subsystem" error message when you run an MS-DOS or 16-Bit Windows program in Windows Server 2003 or Windows 2000 Server

Error

When trying to run an MS-DOS-based or a 16-bit Windows-based command on a Microsoft Windows Server 2003-based or a Microsoft Windows 2000 Server-based computer, you may receive one of the following error messages:
- 16-bit MS-DOS Subsystem
  path to the program you are trying to start or install
  C:\WINNT\system32\config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
- 16-bit MS-DOS Subsystem
  path to the program you are trying to run
  config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
- 16-bit MS-DOS Subsystem
  path to the program you are trying to run
  C:\WINNT\system32\autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
- You may be prompted either to quit the program or to ignore the error message, but the program quits after either option.

Cause

This issue can occur if any one of the following files are missing, damaged, or not located in the %systemroot%\System32 folder: In XP %systemroot% is winnt directory
- Autoexec.nt
- Command.com
- Config.nt

Solution

Insert the Windows Server 2003 CD or the Windows 2000 Server CD into the CD drive.
Click Start
Click Run
Type in the box
Click OK
Type the following commands, and press Enter after each command In the commands below winnt is the directory for XP, if your system is not XP then expand them to your %systemroot% directory
- expand D:\i386\config.nt_ winnt\system32\config.nt
- expand D:\i386\autoexec.nt_ winnt\system32\autoexec.nt
Start or install the program
If the issue is resolved, do not complete the remaining steps
If the issue is not resolved, go to the next step
Start Notepad
Type the following commands.
Note The Command.com file is not edited or created in the following process. Because of this, you may have to expand the file from your CD-ROM.
See *** below for instructions on how to do this Replace %systemroot% with your default root directory for your system.
On the File menu, click Save As
In the File Name box type
Click Save
Close the Config.nt file
On the File menu
Click New
In the new blank document, type the following entries
On the File menu
Click Save As
In the File Name box type
Click Save
Close the Autoexec.nt file
Start Windows Explorer
Locate the Config.nt file
Right-click the Config.nt file
Click Copy
Right-click the %systemroot%\System32 folder
Click Paste
Locate the Autoexec.nt file
Right-click the Autoexec.nt file
Click Copy
Right-click the %systemroot%\System32 folder
Click Paste
*** Expand the Command.com file from the Windows Server 2003 or the Windows 2000 Server CD-ROM. To do this, follow these steps:
- Click Start
- Click Run
- Type in the box
- Click OK
- In the command windows type the following
- Exit
- Restart your computer

ATL.DLL Cannot Be Found

Problem

The problem is that the ATL.DLL has somehow been removed from the c:\windows\systems32\ folder.
The System Restore and everything else Windows relies on will not work

Solution

Before you continue check folder permission so you are allowed access
Expanded the ATI.dl_ file into c:\windows\system32
To expand the file use the Recovery Console
At the WINNI> OR C:\winodws> prompt type
If you can't access this file try the one on the CD, just type in CD D:\i386 and press Enter key if D: is the drive letter of the CD
Press Enter key
Type in at the C:\I386> prompt
Then go to Start
Run and type in
Press Enter
Note: If the file is not on your hard drive expand from the CD-ROM

Windows Could Not Start Because the Following File Is Missing or Corrupt: \Winnt\System32\Config\Systemced

Error

When you restart your Microsoft Windows 2000-based computer, you may receive the following error message
You may also receive the following error message

Cause

This behavior can occur if one of the following conditions is true
- A Promise Technology, Inc. ATA66 PCI controller card is installed in the computer. This issue typically occurs during the Windows 2000 installation process
- The System hive in the registry is damaged or missing
  - Windows 2000 may be unable to load the registry if it is too large. This issue can occur when a process writes too much data to the System subkey in the registry. The System subkey is designed to contain only the information that is necessary to boot the computer.
  - Computers that are based on Intel architecture or ARC (RISC) architecture can only use 16 megabytes (MB) of memory at this stage of the boot process. The System registry subkey has to share the 16 MB with the loader, kernel, HAL, and boot drivers. In some instances, the size of the System subkey may be 13 MB or larger.

Solution

To resolve this issue, use the appropriate method
Reduce The Size Of The System Hive
- If a large number of resources are shared on the computer, the registry may become too large
- To resolve this issue, use the following steps
  - Start registry editor (Regedt32.exe)
  - Locate and click the following key in the registry
  - On the Registry menu, click Save Key
  - In the File name box, type Shares.new
  - Click Save
  - Locate and click the following key in the registry
  - On the Registry menu, click Load Hive
  - In the list of files, click the System.old file
  - Click Open
  - In the Key Name box type System.old
  - Click OK
  - Locate and click the following key in the registry
  - Note: the setting for the Default value
  - Locate and click the following key in the registry
    where x is the number that you noted above
  - On the Registry menu, click Save Key
  - In the File name box, type Shares.old
  - Click Save
  - Restore the Shares.new key to the System.old registry hive
  - Click the HKEY_LOCAL_MACHINE\System.old key
  - On the Registry menu, click Unload Hive
  - Quit Registry Editor
  - Restart the computer to the Recovery Console
  - At the command prompt, type the following lines, pressing Enter after you type each line
  - At the command prompt, type exit
  - Press Enter to restart the computer
Remove the Promise Technology ATA66 PCI Controller
- If this issue occurs during the Windows 2000 installation process and a Promise ATA66 controller is installed in your computer, remove the Promise Technology ATA66 PCI controller card, check your BIOS settings to make sure that the IDE controller on your motherboard is enabled
- Run Windows 2000 Setup again

Your System Has No Paging File, or the Paging File Is Too Small

Error Message

Your computer may seem to stop responding (hang) while Windows is loading your personal settings, or you may receive the following error message after you log on to Windows:
- Limited Virtual Memory Your system has no paging file, or the paging file is too small.
  
  To fix this problem, go to System in Control Panel, click the Advanced tab, and under Performance, click Settings. On the Advanced tab, click Change. Click 'Custom size,' and then type an initial or maximum paging file size.
If you view the configuration settings for the paging file by following the instructions in the error message, you may receive the following message:
After you click OK, the settings for your paging file may seem to be correct.

Cause
- This error message may occur if Windows tries to create a paging file on an NTFS volume, but the System and Administrators accounts do not have the correct NTFS permissions on the volume.
Solution
- To resolve this issue, give the System and Administrators accounts full control of the NTFS volume on which the paging file is configured.
  - If you are running Windows XP Home Edition, or you are running Windows XP Professional but you do not log on to a domain, start your computer in Safe mode.
  - Note: If your computer seems to stop responding while Windows is loading your personal settings
    - Press ALT+TAB to switch to the Limited Virtual Memory dialog box
    - Click OK
  - Click Start
  - Point to Programs (or All Programs)
  - Point to Accessories
  - Click Windows Explorer
  - In the left pane, expand My Computer
  - Click a drive that is configured to use a paging file.
  - To determine if a drive is configured to use a paging file:
    - Click Start
    - Click Run
    - Type
    - Click OK
    - On the Advanced tab
    - Click Settings under Performance
    - On the Advanced tab
    - Click Change under Virtual Memory
    - Click a drive in the list
    - Note: The options that are selected under Paging file size for selected drive
  - Notes:
    - A drive is configured to use a paging file unless No paging file is selected for that drive.
    - If more than one drive is configured to use a paging file, click the first drive in the list the first time that you follow these steps.
    - Click the second drive in the list the second time that you follow these steps, and so on.
  - Click Cancel
  - Click Cancel to return to the System Properties dialog box
  - On the Computer Name tab, note the name before the first period in the Full computer name box. This is your computer name. You will need this information in the following steps.
- On the File menu
- Click Properties
- Click the Security tab to view the current permissions
- Click Add
- Type
- Click OK
- Click Add
- Type
- Click OK
- Click OK
- Note: You must type Administrators, not Administrator
- Click System
- Click to select the Full Control check box
- This automatically selects the other check boxes
- Click Administrators
- Click to select the Full Control check box
- This automatically selects the other check boxes
- Click OK If you want to make changes to your paging file options
  - Click Start
  - Click Run
  - Type
  - Click OK
- On the Advanced tab
- Click Settings under Performance
- On the Advanced tab
- Click Change under Virtual Memory
- Set the paging file options that you want
- Close the System Properties dialog box
- Quit any running programs
- Restart the computer

"Snap-in Failed to Initialize" Error Message When You Open Microsoft Management Console

Error Messages

When you try to open a Microsoft Management Console in Windows XP Professional that involves security policies (such as Local Security Policy, Group Policy, or Domain Security Policy), the console may not open, and you may receive an error message similar to one of the following error messages:
- Snap-in failed to initialize.
  Name: Group Policy
  CLSID: {8FC0B734-A0E1-11D1-A7D3-0000F87571-E3}
- Snap-in failed to initialize.
  Name: Resultant Set of Policy
  CLSID:{6DC3804B-7212-458D-ADB0-9A07E2AE1FA2}
- Snap-in failed to initialize.
  Name: Software Installation (Computers)
  CLSID:{942A8E4F-A261-11D1-A760-00C04FB9603F}
- Snap-in failed to initialize.
  Name:
  CLSID:{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}

Solution

Try one of the following methods
- Method #1
  - Right-click My Computer
  - Click Properties
  - On the Advanced tab
  - Click Environment Variables
  - Under System Variables double-click the PATH environment variable
  - Type
  - Note: If other system variables appear, do not remove them
  - Click OK
  - Click OK
Method #2
- Click Start
- Click Run
- Type
- Click OK
  - Click Expand File
    - Type in the File to restore field
    - Restore the file from the i386 folder on the XP CD
    - Save it to the %systemroot%\System32 folder

Unable to Start Win 16 WOW Applications

Summary

When starting 16-bit Windows applications with Windows NT or XP, if you do not get an hourglass pointer and no application loads when you click the icon for a 16-bit Windows application
This may indicate a corrupt or missing wowexec.exe file.
The Windows On Windows (WOW) function of MS-DOS or 16-bit Windows-based Program and XP is handled by wowexec.exe.
If the file is corrupt, the following error message may appear:

Solution

Windows 3.0 and 3.1 applications are 16-bit and run in WOW in a Virtual DOS Machine (VDM).
There must be a valid wowexec.exe in the system32 subdirectory for the WOW subsystem to start.
If the file is corrupt or missing, the above error message may appear during logon or when attempting to load a 16-bit Windows application.
Check the file size and if it is not correct then replace it or if you don't have the file in the System32 Subdirectory
- The correct file size of wowexec.exe is 15872 bytes.

Task Manager Has Been Disabled by Your System Administrator

Error Message

Task Manager Has Been Disabled by Your System Administrator

Solution

To enable Task Manager, use one of the following methods
- Method 1 Using Command
  - Click Start
  - Click Run
  - Type this command exactly as given below or Copy and Paste into the command box
  - Method 3: Using Group Policy Editor [ Windows XP Professional ]
    - Click Start
    - Click Run
    - Type in
    - Click OK
    - User Configuration
    - Administrative Templates
    - System
    - Ctrl+Alt+Delete Options
    - Remove Task Manager
    - Double-click the Remove Task Manager option
    - Set the policy to Not Configured

Win16 subsystem was unable to enter protected mode, dosx.exe must be present in your path.

Error Message

When the 16-bit Windows or Windows on Windows (WOW) subsystem starts, the following error message is displayed:
Note: The WOW subsystem may be started automatically when you start Windows NT or the first time you run a 16-bit Windows-based application.

Cause

The DOS environment is not properly configured to run 16-bit applications setup file

Solution

Open Notepad or Wordpad

Click File

Click Open

Browse to C:\WINNT\System32 directory

Open the file CONFIG.NT

Look at the bottom of the file for the following syntax:

device=%SystemRoot%\system32\himem.sys

If it is not there add it to the file

Click File

Click Save

Close Notepad or Wordpad

This line may exist but be proceeded by a "REM", which prevents it from being read. Remove the "REM" if this is the case.

If there are other "devices" specified, add "REM" to the line to prevent it from being used in the DOS settings during the install. It is possible to remove the "REM" once setup is complete.

Try setup again

OR the following is from Microsoft Corporation

Cause

One or more of the following conditions exists in Microsoft Windows NT or Windows NT Advanced Server: o
- HIMEM.SYS or DOSX.EXE is missing or corrupt in the SYSTEM32 directory. o
- HIMEM.SYS is not being loaded in the CONFIG.NT file. o
- DOSX.EXE is not being loaded in the AUTOEXEC.NT file
Solution
- Do the following the same way as above
- Make sure that the line, "device=%SystemRoot%\system32\himem.sys," exists in the CONFIG.NT file
- Make sure that the line, "lh %SystemRoot%\system32\dosx.exe," exists in the AUTOEXEC.NT file
- Expand HIMEM.SYS, DOSX.EXE, or both from the Windows NT or XP setup disks or CD- ROM disc if either or both are missing from the SYSTEM32 directory

Error Trying To Access Add/Remove In Control Panel

Error

When you try to open add/remove programs in the control panel you receive an error message.. Additionally, one of the following error messages may appear, the Line Number may differ.:
- An unexpected error occurred. Class not registered
  res://appwiz.cpl/listbox.htc
  Line:225
- Object doesn't support this property or method res://appwiz.cpl/default.hta
  Line: 75

Solution

To resolve this issue, follow these steps:
- Disable System Restore
- First check for spyware/adware
  - CW Shredder, Ad-aware and the online scan program.
- If the problem persists
- Click Start
- Click Run
- Type in the box
- At the prompt, type
- Click okay

"RUNDLL Error Loading irprops.cpl"

Error

When you start a computer that runs Microsoft Windows XP Professional or Windows XP Home Edition, you may receive the following error message:

Solution

Remove the Bluetooth Authentication Agent
- Click Start
- Point to Settings
- Click Control Panel
- Open Add/Remove Programs
- On the Install/Uninstall tab click Bluetooth Authentication Agent
- Click Add/Remove
- Restart the computer
Delete the BluetoothAuthenticationAgent entry from the Windows registry
- Click Start
- Click Run
- Type in
- Click OK
- Locate and then click the following registry key
- In the right pane, right-click BluetoothAuthenticationAgent
- Click Delete
- Close Registry Editor
- Restart the computer

shlwapi.dll Error Messages

All Error Messages for the Shlwapi.dll file have the same solution, replace the file with the correct version..
The problem is some programs when installed download an older version of the file than what is suppose to be used with your Operating System.
Solution
- Two solutions to this problem
  - Download a new file from the internet
  - Use the Recovery Console to reinstall a new file.
  - Installing Windows XP Recovery Console if it is not installed already
  - Boot to Recovery Console. At the "Welcome to Setup" screen, press F10 or press 'R" to repair.
  - Type the following commands and press Enter after each command
  - Note: If the file cannot be found change the path to the CD Drive and insert the XP CD
  - Type Exit and press the Enter Key

"STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME" Error Message When You Restart Your Computer or Upgrade to Windows XP

Error Message:

When you first restart your computer during the upgrade to Windows XP or when you start Windows XP, you may receive the following error message, where aaaaaaaa, bbbbbbbb, cccccccc, and dddddddd are hexadecimal numbers that may vary:
Note:
- If you receive this error message when you restart the computer for the first time during an upgrade to Windows XP, your original operating system still works correctly
- In some cases, a message appears on the BIOS report screen that states that the wrong cable is in use, but you may not see this message on computers that have a fast startup time

Cause

This behavior can occur if either of the following conditions is true:
- Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller, and the following conditions are true:
  - You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable
  - The basic input/output system (BIOS) settings are configured to force the faster UDMA modes
- The file system is damaged and cannot be mounted

Solution

To resolve this behavior, use the appropriate method
- UDMA Controller
  - If your computer uses a UDMA hard disk controller, use the following procedures:
    - Replace the 40-wire cable with an 80-wire UDMA cable
    - In the BIOS settings for your computer, load the 'Fail-Safe' default settings, and then reactivate the most frequently used options such as USB Support
- Damaged File System
  - If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged
  - If this is the case, restart the computer to the Recovery Console, and then use the chkdsk /r command to repair the volume
  - After you repair the volume, check your hardware to isolate the cause of the file system damage
  - To do this, use the following steps:
    - Start your computer with the Windows startup disks, or with the Windows CD-ROM if your computer can start from the CD-ROM drive
    - When the Welcome to Setup screen appears, press R to select the repair option
    - If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console
    - Type the administrator password when you are prompted to do so
    - At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press Enter
    - At the command prompt, type exit, and then press Enter to restart your computer
    - For additional information about how to use the Recovery Console in Windows XP, read the article in the Microsoft Knowledge Base:
      - 314058 (http://support.microsoft.com/kb/314058/EN-US/) Description of the Windows XP Recovery Console
    - If this procedure does not work, repeat it and use the fixboot command in step 5 instead of the chkdsk /r command

Microsoft Digital Image

Error 1606.Could not access network location INSTALLDIR
Out of disk space. Disk space required for installation exceeds available disk space. The selected drive does not have enough space available to install Microsoft Digital Image Library 9. Click the exit setup button, free up additional space on your disk drive, and then run setup again.
Out of disk space. Volume "INSTALLDIR" required space 1kb available space 0 kb. Free some disk space & retry
Error 1317 An error occurred while attempting to create the directory c:\documents and settings\all users\documents\my music

Solution

Click Start
Click My Computer
Right-click C:\
Click the Sharing tab
Note: If the drive C is already shared move ahead to setting Permission
Click New share
In the New Share window, type a name in the Share name text box
Click OK
Click Permissions
In the Permissions window, select the Everyone group in the Group or user names box
In the Permissions for Everyone box, click to select the Allow Full Control check box
Repeat these steps for the My Music folder of the user account that is experiencing the issue
Reboot and try again

DISCLAIMER: The information provided on ALL of these pages is provided as-is. No warranty is provided or implied. Use at your own risk.
Privacy Policy, About Me