Windows Update won't update

In theory, Windows Update is a great timesaving tool. With it, you can check with Microsoft to see if there are any updates for your system and, if necessary, download and install those updates. Windows Update not only provides critical and general updates for Windows, it also can inform you when there are driver updates to your system. The problem is, sometimes those driver updates don’t install correctly when you try to install them. Fortunately, with a quick from Microsoft, you can quickly fix Windows Update.

Author’s NoteAs a general rule, I don’t like to use Windows Update to update drivers on my systems. I’ve had mixed results from the drivers that Microsoft recommends through Windows Update. Sometimes, the "updated" drivers caused more problems than they fixed. For that reason, I suggest that you usually check directly with a hardware vendor before blindly accepting Microsoft-suggested driver updates.

What causes the problem?Windows Update is supposed to check to see what drivers are currently installed on your system and then compare that list against what’s available. According to Microsoft, if there are "a large number" of .INF files in the INF folder in your system directory, Windows Update may incorrectly guess which drivers to install.

Unfortunately, Microsoft doesn’t give any indication about what it thinks a large number is. You can check to see how many files are in your INF folder from either Explorer or a system prompt. When I checked mine, I found over 600 files, so it’s hard to say whether this doesn’t fit the definition of a large number or I’ve just been lucky. Whatever the definition, if you’re having the problem, that’s the reason why.

Fixing the problemYou can quickly fix the problem by downloading a patch from Microsoft. There are two versions of the patch available—one for Windows 2000 and one for Windows XP. Don’t get them mixed up. If you install the wrong patch on the wrong operating system, you’ll cause yourself more problems. The Windows 2000 patch covers all versions of Windows 2000, including the server products. The XP patch covers all versions of Windows XP, including Windows XP Tablet PC Edition.

No matter which version you choose, they’ll both download very quickly. Neither file is bigger than 500 KB. Save the files to a temporary location on your workstation. Before you install the files, make sure you have a recent copy of your system recovery disk and a recent back up.

Once you’ve done that, you can start the installation process. To install the patch, you’ll run the following executables:

· Q814033_WXP_SP2_x86_ENU.exe on Windows XP
· Q814033_W2K_SP4_X86_EN.exe on Windows 2000
Doing so starts a familiar Windows wizard, which will walk you through the installation process. Just follow the on-screen prompts. There aren’t any gotchas along the way to look out for. When the wizard completes, you’re done. You don’t need to reboot or anything else.

A temporary solutionAs annoying as the driver update problem is, you won’t have to worry about dealing with it forever. After you’ve applied this patch, you shouldn’t face it again. Microsoft plans to roll this patch into Service Pack 4 for Windows 2000 and Service Pack 2 for Windows XP, so even if you don’t apply this patch right away, you’ll be covered when those service packs ship.

How To Recover From a Frozen Windows Update Installation

What To Do When Your Computer Gets Stuck Installing a Windows Update

Most of the time, Windows Update does its job with little attention from us. While we might check and install updates manually from time to time, most Windows computers are configured to apply important updates automatically, usually the night of Patch Tuesday.

Sometimes however, when the patch, or maybe even service pack, is being installed during shutdown or startup, the update installation stops - freezes, locks up, hangs, clocks, whatever you want to call it.

The installation of one or more Windows updates is probably frozen if you see one of the following messages persist for a long time:

"Preparing to configure Windows. Do not turn off your computer."

"Configuring Windows updates x% complete Do not turn off your computer."

"Please do not power off or unplug your machine. Installing update x of x..."

You might also see a "Stage 1 of 1" or "Stage 1 of 3" or a similar message prior to the second example. There might be some wording differences too depending on which version of Windows you're using.

It's also possible that no message at all will be displayed and you'll see just the Windows logon screen background. However, if you don't believe that Windows tried to install updates prior to this problem, you should instead troubleshoot using this tutorial: How To Troubleshoot Stopping, Freezing, or Reboot Issues During Windows Login

.
Cause of Windows Update Freezes
There are several reasons why the installation or finalization of one or more Windows updates can hang.

Most often, these types of problems are due to a software conflict or a preexisting issue that simply wasn't brought to light until the Windows updates started installing. Much more rarely they're caused by a mistake on Microsoft's part regarding the update itself.

Note: There's an actual issue with Windows that can cause Windows Update installations to freeze like this but it's only applicable to Windows Vista and only if SP1 hasn't yet been installed. If your computer fits that description, install Windows Vista SP1 or later or this update to solve the problem.

Verify The Problem
Some Windows updates can take several minutes or more to configure or install so you want to make sure the updates are truly stuck before moving on. Trying to fix a problem that doesn't really exist will just create a problem.

You can tell if Windows updates are frozen if nothing happens on screen for 30 minutes or more. If there's any wonder after that long, take a look at your hard drive activity light. You'll see either no activity at all, or very regular but very short flashes of light.

Chances are that the updates are hung long before 30 minutes but this is a reasonable amount of time to wait and probably twice as long as I've ever seen a Windows update take to successfully install.

Troubleshooting Steps

1.Restart your computer, using either the reset button or by powering it off and then back on using the power button. Hopefully Windows will start normally and finish installing the updates.

I realize that you're probably explicitly told not to do this by the message on the screen, but if the Windows update installation is truly frozen then you have no other choice but to hard reboot.

Tip: Depending on how certain settings in BIOS are configured, you may have to hold down the power button for three to four seconds before the computer will turn off.

Note: If you're automatically taken to the Advanced Boot Options menu after restarting, choose Safe Mode and see the comments in Step 2 below.

2.Start Windows in Safe Mode. This special diagnostic mode of Windows only loads the minimum drivers and services that Windows absolutely needs so if another program or service is conflicting with one of the Windows updates, the install might finish up just fine.

If the Windows updates do install successfully and you continue to Safe Mode, just restart from there to enter Windows normally.

3.Complete a System Restore to undo the changes made so far by the incomplete installation of the Windows updates. Since you can't access Windows normally, try doing this from Safe Mode. See the link in Step 2 if you're not sure how to start in Safe Mode.

Note: During the System Restore, be sure to choose the restore point created by Windows just prior to the update installation.

Assuming a restore point was made and System Restore is successful, your computer should be returned to the state it was in before the updates started. If this problem occurred after automatic updating, like what happens on Patch Tuesday, be sure to change Windows Update settings so this problem doesn't reoccur on its own.

4.Try System Restore from the System Recovery Options (SRO) menu if you're not able to access Safe Mode or if the restore failed from Safe Mode. Since the SRO menu is available from "outside" of Windows, you can try this even if Windows is completely unavailable.

Important: System Restore is only available from outside of Windows if you're using Windows 8, Windows 7, or Windows Vista. This option is not available in Windows XP.

5.Complete a Startup Repair. While a System Restore is a more direct way of undoing changes, in this case a Windows update, a Startup Repair (or Repair Install in Windows XP) could be helpful if a System Restore isn't successful for some reason.

6.Test your computer's memory. It's possible that failing RAM could be causing the patch installations to freeze. Luckily memory is really easy to test.

7.Update BIOS. An outdated BIOS isn't a common cause for this problem but it's possible.

If one or more of the updates Windows is trying to install is involved with how Windows works with your motherboard or other built-in hardware, a BIOS update could solve the issue.

8.Clean install Windows. A clean install involves completely erasing the hard drive that Windows is installed on and then installing Windows again from scratch on that same drive.

Obviously you don't want to do this if you don't have to but it's a very likely fix if the troubleshooting steps prior to this one were unsuccessful.

Note: It might seem likely that reinstalling Windows, and then these same exact Windows updates, will cause the same problem but that isn't usually what happens. Since most lock-up issues caused by updates by Microsoft are actually software conflicts, a clean install of Windows, followed promptly by the installation of all available updates, usually results in a perfectly working computer.

Please let me know if you've had success escaping a hung Windows update installation using a method I don't have included in the troubleshooting above. I'd be happy to include it here.

Applies To
Any of Microsoft's operating systems could experience freezing issues during Windows updates including Windows 8, Windows 7, Windows Vista, Windows XP, and more.

Still Having Freezing Issues Related to Windows Update?
Let a community of computer support enthusiasts help out! Post the details of your problem in the PC Support Forum. Be sure to let us know exactly what's happening, what updates you're installing (if you know) and what steps, if any, you've already taken to try to fix the problem.

Releasing Windows 8 - August 1, 2012

Today marks an important milestone in the Windows 8 project. The Windows 8 team is proud to share with you that a short while ago we started releasing Windows 8 to PC OEM and manufacturing partners. This means our next milestone will be the availability of exciting new models of PCs loaded with Windows 8 and online availability of Windows 8 on October 26, 2012.

Back when we first demonstrated Windows 8 in May 2011, we described it as “reimagining Windows, from the chipset to the experience,” and that is what Windows 8 (and Windows RT) represents for both Microsoft and partners. The collective work: from the silicon, to the user experience, to new apps, has been an incredibly collaborative effort. Together we are bringing to customers a new PC experience that readies Windows PCs for a new world of scenarios and experiences, while also preserving an industry-wide 25-year investment in Windows software.

We continue to be sincerely humbled by the breadth of participation in our pre-release testing. The previews of Windows 8 (Developer, Consumer, Release) have been the most widely and deeply used test releases of any product we have ever done. Over 16 million PCs actively participated in these programs, including approximately 7 million on the Release Preview that started 8 weeks ago. The depth and breadth of testing validate the readiness of Windows 8 for the market.

The openness of the previews presents a unique perspective on product development, and we’re deeply committed to the transparency of the preview process. No product used by so many people in so many different ways is developed “out in the open” like Windows 8 has been. This blog, the forums, and the preview releases form an important part of the development process. Major changes have been made at each milestone and as we promised, the final release (build 9200, for those tracking) contains many promised refinements. We are humbled by the responsibility of meeting the needs of such a diverse set of customers and enthused by the deep level of participation in the pre-release process.

While we have reached our RTM milestone, no software project is ever really “done.” We will continue to monitor and act on your real world experiences with Windows 8—we’ve used the preview process to test out our servicing and we have every intent of doing a great job on this next important phase of the product. Hardware partners will continue to provide new devices and improve support for existing devices. PC makers no doubt have quite a bit in store for all of us as they begin to show off PCs specifically designed for Windows 8.

With improvements in fundamentals, enhanced storage and connectivity, newly architected subsystems, the “fast and fluid” user experience, and the WinRT platform (to name a few), Windows 8 has literally thousands of new features. We did a record number of blogs posts (and videos) and did not even come close to covering the full breadth of Windows 8. There’s much left to learn about and discover in the product.

Some of the most exciting innovations with Windows 8 are yet to come—the innovations from developers building apps on the new WinRT platform. Today, the Store is open for business and we’ll rapidly expand to over 200 markets around the world. The opportunity for developers around the world to deliver innovative (and profitable) apps is unique with Windows 8. We’re excited to see the work developers will be bringing to Windows 8. We’ll also have a chance to talk more about the Windows 8 platform at the next BUILD conference recently announced.

We know there are lots of questions about how to get Windows 8 and when, and of course more questions to come about exploring and using the full set of thousands of Windows 8 features. Our Windows Team Blog today has posted a lot of new information and gathered up some important details that we hope will answer your questions. Please check our blog and stay in touch on the in-market developments of Windows 8 there.

On behalf of the Windows 8 engineering team, we want to thank you very much for your contributions throughout development and your contributions yet to come to Windows 8. THANK YOU!


Next stop, October 26, 2012 and General Availability!

Three Killer Problems That Threaten Windows 8

Brad Wardell, president and CEO of software company Stardock, recently said that the upcoming Windows 8 operating system is so severely flawed that it will hurt the PC experience and, therefore, PC gaming. How bad does he think Windows 8 is?

Since he's using the preview version and runs a successful PC software company that also publishes some great games, we figure he's a qualified expert. We asked him to explain (since we've also heard some wonderful things about Windows 8). He obliged.

Here's Brad:

Windows 8 has a lot of features to recommend it. It's smaller. It's faster. It's smoother. However, it has three flaws that worry me a great deal.

#1 It's schizophrenic. Is it a tablet OR a desktop OS? It tries to be both…and neither.
Let's say you're on the desktop and you want to load up Mass Effect 3 or Microsoft Word. You are expected to move your mouse to the bottom left, wait for a tile to be displayed, click on the tile. That action whisks you away from the desktop to the Metro environment where you can then look for those programs.

The Windows 8 experience involves jumping back and forth between the tablet environment (Metro) and the desktop. They have nothing in common. Metro's task list won't list desktop apps and the desktop won't list recently active Metro apps. They're separate and yet you have to use both.

#2 Forcing apps to be full screen is obnoxious. Imagine Notepad running full-screen with no border, no title bar, and no menu bar on a 21 inch monitor. That's what a Metro text editor would be like to use.
Metro apps want to be full-screen. Always.

You can snap them to use 1/3rd or 2/3rd of the screen, vertically, but that makes usability even worse in most cases. Take your most common apps and resize them vertically as mentioned and tell us what you think of that.

Try getting any serious work done like this.

#3 It's a usability nightmare. Let's assume you can accept/adapt to items 1 and 2. You're adaptable. What's the problem? Answer: The rest of the user base.
Less savvy users are in for some serious grief.

Nothing is visually discoverable. There are no visual cues. It's all based on touch, which means for most users, moving the mouse moving around the screen until it finds an invisible hotspot.

There's no Start button or Start menu on the desktop (unless you use a third-party utility like Start8 which is not going to be acceptable for corporate customers).

Multi-monitor user? Forget it. Metro doesn't support multiple monitors, at least presently. Additional monitors can be the Windows desktop but Metro always reserves one monitor for itself.

Why are they doing this? I can't think of any reason why they would do this—except for the hypothesis that they are obsessed with some group of users who would be better off with a tablet.

Take a look at Microsoft's own promotional video

This isn't a "one in a series" video. This is THE video promoting Windows 8 right now. What does that video tell you about Windows 8?

Other than three seconds at the tail end showing someone on the desktop, it's all about using it as a tablet OS. I don't mind Metro being included. I mind being forced to jump between it and the desktop to get anything done.
Move your mouse to the top left and swipe down. You get this list of things that are running.

This is the Metro version of Internet Explorer. How do you create another tab? No idea. Does it support tabs? No idea. Windows 8 also includes a traditional Internet Explorer too but you can't easily switch between the two.

This is what one of Microsoft's included Metro apps actually looks like when you first run it. That back button does nothing.

This is what Metro looks like on a system running a typical screen resolution.

Microsoft: You can't party like 1999 anymore.

I've seen Windows 8 advocates say that if you don't have a tablet you should just stick with Windows 7. I think a lot of people may do that.

But here's the problem for Microsoft: This isn't 1999 where they could ship a Windows ME type product and users had no real alternatives. 2012 is the year in which millions of users are using an iOS or Android device.

By the time Windows 8 is released, it's going to be facing a market where displays are going start including AirPlay and/or Intel WiDi. That means mobile devices will be able to stream their output to large screens. Connect a Bluetooth keyboard, mouse, gamepad and suddenly that mobile device could become a real threat.

I'm a PC developer. I want Windows 8 to succeed. I have Windows games and software in development with releases dates far in the future. It's a pretty big deal to us that Windows 8 not fail.

Lest you think I'm yelling about falling skies or preaching doom, let me say that I have great faith that between now and the time Windows 8 ships that someone at Microsoft will realize the peril they're putting their flagship OS in.

Microsoft can fix these issues before Windows 8 ships. Don't force users to jump around between Metro and the desktop. Allow users to live within a single, consistent environment if they so choose. All we need is for Microsoft to release a solid, non-crazy version of Windows 8.
Brad Wardell is president and CEO of Stardock. He's been previewing Windows 8 for some time. Stardock is a Microsoft Gold Certified Partner. The company is the world's largest Windows desktop customization software provider with products like WindowBlinds, the Object Desktop suite, Object Dock, Fences and more. They also publish the hit strategy game Sins of a Solar Empire.

Window Problem FAQs

Below is a list of common problems people encounter with their windows and patio doors. We’ve provided solutions and suggestions for each. Just click on a problem to see our recommendations.

Your windows or doors let in too much cool air in winter and warm air in summer.
Old, worn-out windows or patio doors are often leaky, which can result in high energy bills during peak heating and cooling months. The glass may be loose (in which case it should be re-glazed) or the seal between the sash and frame may have weakened. The cost of replacing failing windows is often dwarfed by overall household energy costs, but we recommend replacing old single-pane windows with modern windows that feature dual-pane Low-E glass for a substantial energy savings. If your windows are in decent shape but still leak, consider applying new weather stripping. It’s easy to install and available at most building supply stores.

Your windows look ugly to you.
“Ugly” is a matter of taste, but let’s address three obvious causes:

Does the exterior color of the windows match the rest of the home? If not, a simple repaint can solve the problem. If the windows are obscured on the home exterior by unattractive storm window frames, consider replacement windows with dual-pane Low-E glass instead.

Does the window style not match the home? Older homes usually feature double-hung windows. Gliders and casement windows offer a more contemporary approach. Consult an expert to see if you need a touch of architectural authenticity in your home.

Does the window or patio door material seem artificial or cheap? If you don’t like the look of thick vinyl frames, replace them with natural wood that can be painted or stained to match your interior.

Your windows won’t open at all.
In some cases, a window may fail to operate simply because of broken hardware. Replace the hardware and the problem is solved, right? Some situations aren’t so easy. Your window, for example, may be painted shut -- and setting it free can be a painstaking process. By carefully working a putty knife around the perimeter of the sash and breaking the paint seal between sash and frame, you can often undo the damage. For some extra leverage, try a small pry bar. In extreme cases the interior trim may have to be removed. Be advised: windows that are painted shut are often older and of poor quality. Replacement windows and patio doors are the best bet.

Operational trouble can also stem from a warped frame and sash. Warped windows or patio doors are usually caused by house settling, which skews the rough opening where the window sits. In this case, the entire window or patio door must be removed and the opening reframed and squared. After that, the most common course of action is to insert a brand new window or door.

Your double-hung window won’t stay open.
If it’s an older window, there’s most likely a problem with the connection to the sash weights. Older double-hung window sash are counterbalanced with heavy weights connected to the sash on a rope. As the windows age, the rope dries out and becomes brittle, eventually breaking. If you decide to fix the problem yourself, you can remove the interior trim to expose the fallen weight, replace the rope and reinstall the trim. Newer double-hung windows often feature in-sash balancers. If these break, follow the window or door manufacturer’s recommendations for balancer replacement.

Your windows don’t open or close easily.
For casement windows, the solution may be as easy as cleaning and lubricating the operating hardware with a light oil or dry silicone spray. Avoid lubricants or harsh abrasive cleaners -- these will break down or collect dirt and grime. Gliding window tracks also need periodic cleanings to maintain easy sash operation. Otherwise, you may be looking at a warped frame and sash caused by house settling, which can skew the rough opening the window sits in. Here, we recommend removing the entire window and reframing and squaring the opening. Then simply insert a new window.

Your windows are difficult to clean.
Some homes must weather tough environmental conditions by virtue of their locations -- such as areas of heavy industry, or along the coast. Airborne particles abound in these environments, and they stick to windows. That means frequent washing. Thankfully, some window products are available to help ease the chore. Many double-hung windows now feature tilt-in sash designs. This means the exterior glass can be cleaned from the inside -- just tilt the sash inward. If grilles cause cleaning headaches for you, consider ordering windows with grilles built-in between the glass. It’ll be easier to wipe the windows clean. If replacement is an option for you, Andersen 400 series windows and patio doors come standard with glass that stays cleaner with less water-spotting. When activated by the sun, this High-Perfomance® Low-E4® glass helps make cleaning easier --while mainting all the benefits of High-Performance Low-E glass such as energy efficiency and sound reduction.

Your windows are falling apart or rotting.
If a window or patio door is failing or on the verge of failure -- leaking, sticking or falling apart -- it’s time to replace it. Choose a style that matches the other windows in your home. In many cases, you can take the opportunity to do more than a simple replacement. Why not enhance your home’s look from the inside and out, and improve your overall energy efficiency? Two windows side-by-side, called a combination, can be replaced with a single picture window that frames a stunning view or opens the room to more light. You can also enlarge an opening to add more windows. Be sure to choose a replacement that features the energy-efficiency of Low-E glass and the durability of rigid vinyl cladding.

Your windows are inconsistent with the style of your home.
If your windows or patio doors don’t match your home’s architectural style, go ahead and replace them with a more appropriate style. It can improve the look of the whole house. Older or more traditionally-designed homes usually feature double-hung windows, while contemporary architecture favors casement or gliding windows. Consult your architect for the best fit.

Moisture is collecting on your window interiors.
Most interior condensation problems are the result of poor household ventilation. By controlling your home’s humidity, you can usually limit interior window condensation. For more information, see our Care & Maintenance section.

You are tired of painting your window exteriors.
The semi-seasonal touch-ups demanded by unclad windows can be a tiring, frustrating business. Want to eliminate this job for good? Replace your current windows with vinyl-clad windows. Andersen® products feature Perma-Shield® vinyl cladding, a system that eliminates scraping, sanding and painting.* And Andersen interiors are solid wood, so you get the best of both worlds -- beauty coupled with convenience.

Solve Any Windows Problem with Event ID

To paraphrase from the ditty “˜Don’t Quit’ ““ When things go wrong as they sometimes will; don’t quit. Because for every Windows crash there’s a way to lick the problem without dialing assistance.

Windows glitches, errors and crashes are a pain in the rear. More often a reboot (or a smack on the sides) is a quick fix. It gets the work done but it still leaves the puzzler out there ““ why did the system crash in the first place?

To remove the vulnerability (we know that Window’s has tons of them!) and troubleshoot errors, it’s necessary to diagnose and cure. This is where the Event Viewer makes a worthy entrance.

An event, as described by Microsoft, is any significant happening in a system or in a program that should be brought to a user’s attention. It can be a system crash, an application freeze or the ominous “˜Blue Screen of Death‘. The notification is duly logged by the system in a log (the event logs) which we can see using the Event Viewer. The Event Log Service registers application, security, and system related events in Event Viewer. Thus we can pinpoint the exact source of a problem and diagnose to prevent future errors.

The Event Viewer has been a part of the Windows OS since the early days of Windows NT. InWindows Vista, it has been modernized to Windows Event Log. In Windows XP, the Event Viewer can be found under Control Panel – Administrative Tools – Event Viewer. That’s where we are now headed for some familiarization.

The Three Logs

Windows XP logs events basically in three logs ““ Application Log, Security Log and System Log. Additional logs may be created by other applications like anti-virus and Internet Explorer.
In Application Log events are posted by programs. For instance, a program hang is reported here. The reporting though depends on the program; if it has been coded to report events.
In Security Log security violation related events like valid and invalid logons are posted. It also records things like clock adjustments and file sharing permissions. This log is disabled by default and only a user with administer privileges can view this log.
In System Log, events related to system failures like startup errors (for instance a failed driver), hardware crashes (a webcam froze) et al find a mention.
How to Read the Event Viewer
The Event Viewer is structured around easy to understand information like – theDate and Time of each event are given with the Source of each problem. The source can be a program, a single file of a program or a system file. The View menu has a Filter which lets you sort the log information in a few ways.
Most of the logs are of the Type “˜Information’. But some types like “˜Errors‘ and “˜Warning’ are worth looking into. (The Security Log also has the Success Audit or Failure Audit types.)
The Error Properties box comes up with a double click. The box provides a slightly elaborate description about the specific error. There is a link provided which links to Microsoft Support. The details of the error can be sent but more often than not it fails to provide a solution.

Event ID is the column which gives us a number to work with. Using this number, we can track the error type and learn about it in more detail. This is the same number which is used by the support guys for troubleshooting. Note: Event IDs may change over time with installation of service packs and patches.
Using the Event ID to Target and Solve


The Event ID numeric value is a key identifier for the problem. The web is a good place to do some DIY troubleshooting.

EventID is a rich database of logged events. The site has a repository of 10,496 event IDs and 497 event sources with a lot more info provided by contributors. Enter the Event ID number and the Source and the site’s search engine filters out the possible resolutions for the particular event. Most of the solutions are contributed by users from their experience. Non members can search using basic search. Paid subscribers get better features like an advanced search and searching for event IDs from a specific source.

Some other search features available for all users are ““
Copy paste the log entry for search
Lookup error codes other than Windows event IDs
Redirect Microsoft’s error lookup link to EventID.net with a registry fix.

Getting all your answers through the website or with a general web search might not ultimately solve the problem. But it will give you a better grasp of things before you call in the boffins.

Using Event ID is just one way. Previously we looked at a few other diagnostic ways to vault over ‘run of the mill stuff’ like stalled Windows. Here’s a small troubleshooter’s list ““

Common Windows Problems and Repairs

Invalid Backweb Application

When I log on to Windows, I get runner error "invalid backweb application, id 137903", how do i fix this?.

You have downloaded a program that contains spyware or adware. The spyware or adware has been removed but the program requires the spyware to be installed in order to run, without it you will get the Run Time error. This program runs on startup so you will have to uninstall the program that had the spyware associated with it. Run Msconfig from the Start > Run window and turn off the progam that you downloaded, or uninstall the program.

If you still cannot find the program do a search for files that contain the word "Backweb"

Changing the Windows logo screens
In Windows 95, 98, and ME the startup logo screen is controlled by the file C:\Logo.sys.If this file does not exist, Windows will load the default logo screen that is inside the file C:\IO.sys. The Please Wait and shut down screens are located in the Windows folder, they are Logos.sys and Logow.sys. If they do not exist Windows will load the default screens. ( words, not pictures). ME does not come with a Please Wait screen.

If no screens are seen you will need to remove the read only attribute from the file C:\Msdos.sys and edit the value Logo=1 if it is set to zero then no screens will be displayed. See the contents of the Msdos.sys File

In the Windows NT platform (NT, 2000, XP)the startup screens are in the Windows folder, named Lanma256.bmp,Lanmannt.bmp, Winnt.bmp, or Winnt256.bmp. They are loaded only if the file exists.

Date is not displayed correctly
If you have a problem where the date is not always displayed correctly on some programs you need to check in two places. In RegEdit go to HKEY_CURRENT_USER\Control Panel\International a value name of "sShortDate" should display the format you want. Example "mm/dd/yy". If the value name "sShortDate" does not exist here then your machine is set to the default "m/d/yy". However you may wish to add the value name and a setting. You will also need to check the Win.ini file, look for the section "[intl]" and set sShortDate=mm/dd/yy or what ever format you wish. The Win.ini must have this entry

Context Menu slow to open
If your context menu (the menu appearing when you right click) is slow to appear (open) then you need to change the MenuShowDelay setting. In RegEdit go to HKEY_CURRENT_USER\Control Panel\Desktop and fine the MenuShowDelay value. If it does not exist create a new string value and name it MenuShowDelay. The default setting is "400" lower it, or try setting it to "200"

Thumbnails will not display
In order for Windows to display Thumbnails, Windows creates a Desktop.ini file and adds it to the folder you want to have a thumbnail view. The value of the HKEY_LOCAL_MACHINE\ Software\ Microsoft\ Windows\ CurrentVersion\ Installer\ Products\ 9040B11900063D11C8EF00054038389C\ ProductNonBootFiles
is changed to "Usage"=dword:2c4c025a

Files such as BMP that you wish to display as thumbnails should have a shellex value pointing to
HKEY_CLASSES_ROOT\ CLSID\ {7376D660-C583-11d0-A3A5-00C04FD706EC} and the file
C:\WINDOWS\ SYSTEM32\ BROWSEUI.DLL must be present and not corrupted. This entry should look like "{7376D660-C583-11d0-A3A5-00C04FD706EC}" . BROWSEUI.DLL must be registered properly for the thumbnails to display.

Then on each folder for which you want Thumbnail view capabilities, you must right click the folder, select Properties and check the box Enable Thumbnail view.

Unable to copy and paste
If you ever find that you are unable to copy and paste in the Windows Explorer, open the Control Panel. Select the Internet Options applet and click on the Security tab. Then click on Custom Setting, find the option "Drag and copy or paste" and ensure that it is enabled.

Changing bulk entries in the Registry
Have you ever needed to change a lot of entries in the Registry.? Well here is a common problem when the Registry becomes corrupt. From a customer:
"... the numerous entries the Registry Drill has been finding which have a '?' in the path name, like this:
C?\PROGRAM FILES\COMMON FILES\Microsoft Shared\TextConv\MSWRD832.CNV"

This is an invalid path. The question mark, "?" should be a colon, ":". The entries were probably made either by a corrupted setup program or by a corrupt Registry. The colon character was unreadable to RegEdit and it interprets the character as a question mark.

The easy way to repair this is to export the Registry to a text file. Open it in Wordpad and have Wordpad do a search and replace; search for "C?\\ and replace all with "C:\\. Then do it again but this time instead of seaching for "C?\\ search for (space)C?\\

Registry has errors every boot
Do you get the message "Windows encountered an error accessing the system Registry..." every time you boot to Windows 98 or ME? Here is a simple trick, first use the Ctrl-Alt-Delete button to close down the Windows Registry Checker. Then do a search on the Windows Drive for User.dat, normally you may find one in your profiles folder. If you do check the byte size, and if it is a zero byte file, Windows made a bad copy of it and wants to replace it but it cannot. It already backed up a bad copy. So just delete it, or replace it with the one in the Windows folder.

If no file is found and/or this does not cure the problem and you had the foresight to make an exported copy of the Registry prior to this you're now in great shape. You can now always replace the Registry with a new one. Move the file to your Windows folder and from a DOS prompt get to the Windows directory (folder). At the Windows Prompt type :
Smartdrv.exe /v and then press the Enter button. Then type :
RegEdit /c backup.reg (replace Backup.reg with the name of the file you named your export file)

You now have a new Registry database installed

Replacing Windows Splash Screens
The Windows 9x startup splash screen is controlled by the file C:\Logo.sys. If the file is present the image in the file will appear when booting to Windows. If not, the standard Windows splash screen is inside the file C:\IO.sys . The file IO.sys is more than a bmp file so do not change this file with a bmp. In Windows ME the startup screen is controlled by the IO.sys file. And adding a Logo.sys file seems to not work. You must also have the setting Logo=1 in the MSDOS.sys file for the splash screens to work.

The Windows 95 Please wait is controlled by the file Logow.sys in the windows folder, Windows 98 is Logow.w98, ME does not use this file. The shut down screen is controlled by the file Logos.sys also in the Windows folder.

Customizing the logo screen file must be 320 x 400 in size and 256 in color; RGB encoded bmp file.

Setup stops on Windows 2000/Windows XP
There are several reasons why setup will hang, but I did find the work around. After checking all the settings in the BIOS and reading MS knowledge base I figured out that the BUS Master IDE controller was not compatible with Windows XP and Windows 2000. I found that pressing the F7 instead of F6 (as prompted) key when setup asks for a RAID or SCSI driver allowed me to install both 2000 and XP. After pressing the F7 key You need to wait a few minutes for setup to continue.The F7 key will tell setup to install a different driver then the default driver.

If the F7 key trick does not work you need to start removing hardware. Also if you have Goback or similar software you need to disable it.

Unable to open files on my zip drive
Here is the question I received:
I am having a problem with trying to open files stored on a zip drive. I have been using these files over the past several months all using Fast View to open the files. The files show that they have been previously opened with Fast View since the files on the disk all show the Fast View Logo. Every time I try to open these files I get a message saying that "The format of this file is not supported by Fast View".

You can try copying a file or two to your hard drive and see if you can open it there. If not than the FAT has been corrupted. If you used the Zip Disk on an NT machine try reopening the files on that machine. ( I have personally found that if I created a Zip Disk on a Windows 9x machine and attempted to view them on an NT machine the FAT would become corrupted if the Zip Drive unit was hot.)

Control Panel Applet cannot be loaded
Here is the question I received:
When I click on control panel. I get a message that tells me that an applet cannot be loaded. What does this mean and how do I fix it?

If you get a message box that states a resource or applet cannot be loaded this normally means one of two things. 1) The applet file (.cpl) associated with the applet not loaded is corrupt. 2) The Registry information for that applet is corrupt or the Key containing the needed information is corrupt.

First, attempt to replace the cpl file and reboot. With Windows ME you can delete the file and Windows will replace it automatically if it is a standard Windows applet. If this does not work you will need to restore the Registry with a good backup.

If the applet in question is not needed, you can add a line in the Windows\Control.ini. Assuming that the applet is the joystick applet and you do not have a joystick then the entry will look like the following:
[don't load]
joystick.cpl=no
Be sure you locate the correct file in the System or System32 folder and enter the correct file name.

Out of memory error
Out of memory errors are normally a catch all error. Meaning when an error occurs that is not planned on the error falls passed the expected errors and displays this message. There is some error in the program like to much information being posted within the program. Example: a program is listing the files in a folder and there are more then 32,786 files the programmer did not plan on this so you may get the Out of memory error. Or a program is loading and not all its required files are present for it to get all the required information for it to load, you may get this message.

Windows Installer error
The Windows Installer service could not be accessed' on Windows XP?

When you attempt to install a program that uses Windows Installer, such as Office XP, you receive: "The Windows Installer service could not be accessed. This can occur if you are running in safe mode or if the Windows Installer is not correctly installed. "

This error is probably the result of a damaged registration service. To resolve this issue:
1. Open a CMD.EXE prompt.
2. Type msiexec /unregister and press Enter.
3. Type msiexec /regserver and press Enter.

Command Interpreter not found
When you get this message it means that the file Command.com was not found. Either because it is missing from the boot drive or your boot drive is not working. The file could also destroyed because of a FAT error. Command.com is used on Windows versions that load on DOS such as Windows 3.0, 95, 98, and ME. Command.com is not used on NT, 2000, XP. They use the file NTDRL to load. The BIOS reads the boot section of the drive to know which file to load. If the system is on the NT platform and you get this error then the boot sector is damaged or the hard drive is damage.

Files open with incorrect program
When you click on a file type and it opens with a program that cannot view it, or the incorrect program it is assoicated incorrectly in the Registry. Example: You want to open a DOC file and Windows Media trys to open it. To repair the file extension find a DOC file, hold the shift key down and double click on it. The Open With dialog window will be displayed. Now seletc the program you want to open the file with, in this case you would select Wordpad or Word. Place a check mark in the box "Always open with" and click "Open". Now all your DOC files will open with Wordpad.

Windows cannot find Program.exe to open ...
Do you get a message for Windows stating " ... cannot find ?????.exe" to open this file type? Well this is easy to repair. Locate the file type (file extension) in the Windows Explorer, while holding the Shift key down right click the file. The context menu will appear with the "Open with" option. Select it and locate the program on your hard drive that you want to open this file type with. Make sure that you check the box on the Open with windows that say "Always open with". Windows will change the need entries in the Registry to make that file type always open with the program you have selected.

Fix Windows Errors Right Away

No one wants to encounter windows errors. It becomes more annoying if the error appears while you are working and corrupts all your important files. Sadly, this error will continue to appear and will not stop to annoy us if not given proper attention and solution. These messages appear because there could be a serious problem with your PC. This Windows Errors needs to be fixed right away. If you do not know what to do, you can rely on the internet to help you windowsエラー修復, or you can rely on computer technicians to do their job.

The first thing you need to do is know the condition of your PC that is having an error. Your PC will often slow down and windows notification will appear on your screen telling what kind of errors your PC is encountering. Often times the system registry of your PC encounters the problem. The system registry contains pieces of information such as the commands, data and files. All are found there. It is where the PC gets all the information needed to perform its specific task. If your PC slows down than the usual, it only means that your PC is having a problem gathering the necessary information to perform a task. This is usually because it contains too much information and resulting for it to clog. So if you encounter such, how do you windowsエラー修復 like this?

If you encounter error that does not allow you to start your PC, installing another clean version of its OS is not always the answer. Try first using Windows restore registry. Microsoft provided specific instructions that will help you solve this problem. But if your problem is just your PC slowing down, there are few simple steps that you can do.

First is to take a look at all the programs installed in your PC. Go to Control Panel and look for “Programs and Features”. Review all the softwares installed in your PC. If the application is not needed deleting it will help you minimize and fix windows errors. If there is a problem with one of your PC’s software and you still need it, re-installing it will restore its performance.

Second is to run “Msconfig.exe”. it is a system tool to help you find what could be the problem with your PC’s startup process. You can look here the software or device driver that might be causing why your PC slows down. Try to disable the software that might be causing the error. The primary use of MSConfig is to edit files and provide simplified GUI to control Windows configuration data.

Third is to run registry tool cleaner. This will help you to monitor the PC’s system registry and find files that are needed that might be causing the error. The cleaner removes invalid entries and helps your PC run faster.

Of course there are hundreds of solutions you can find online to help you fix windows errors. But taking care of your PC is the best solution.

list of window error codes

0 ERROR_SUCCESS: The operation completed successfully.
1 ERROR_INVALID_FUNCTION: Incorrect function.
2 ERROR_FILE_NOT_FOUND: The system cannot find the file specified.
3 ERROR_PATH_NOT_FOUND: The system cannot find the path specified.
4 ERROR_TOO_MANY_OPEN_FILES: The system cannot open the file.
5 ERROR_ACCESS_DENIED: Access is denied.
6 ERROR_INVALID_HANDLE: The handle is invalid.
7 ERROR_ARENA_TRASHED: The storage control blocks were destroyed.
8 ERROR_NOT_ENOUGH_MEMORY: Not enough storage is available to process this command.
9 ERROR_INVALID_BLOCK: The storage control block address is invalid.
10 ERROR_BAD_ENVIRONMENT: The environment is incorrect.
11 ERROR_BAD_FORMAT: An attempt was made to load a program with an incorrect format.
12 ERROR_INVALID_ACCESS: The access code is invalid.
13 ERROR_INVALID_DATA: The data is invalid.
14 ERROR_OUTOFMEMORY: Not enough storage is available to complete this operation.
15 ERROR_INVALID_DRIVE: The system cannot find the drive specified.
16 ERROR_CURRENT_DIRECTORY: The directory cannot be removed.
17 ERROR_NOT_SAME_DEVICE: The system cannot move the file to a different disk drive.
18 ERROR_NO_MORE_FILES: There are no more files.
19 ERROR_WRITE_PROTECT: The media is write protected.
20 ERROR_BAD_UNIT: The system cannot find the device specified.
21 ERROR_NOT_READY: The device is not ready.
22 ERROR_BAD_COMMAND: The device does not recognize the command.
23 ERROR_CRC: Data error (cyclic redundancy check).
24 ERROR_BAD_LENGTH: The program issued a command but the command length is incorrect.
25 ERROR_SEEK: The drive cannot locate a specific area or track on the disk.
26 ERROR_NOT_DOS_DISK: The specified disk or diskette cannot be accessed.
27 ERROR_SECTOR_NOT_FOUND: The drive cannot find the sector requested.
28 ERROR_OUT_OF_PAPER: The printer is out of paper.
29 ERROR_WRITE_FAULT: The system cannot write to the specified device.
30 ERROR_READ_FAULT: The system cannot read from the specified device.
31 ERROR_GEN_FAILURE: A device attached to the system is not functioning.
32 ERROR_SHARING_VIOLATION: The process cannot access the file because it is being used by another process.
33 ERROR_LOCK_VIOLATION: The process cannot access the file because another process has locked a portion of the file.
34 ERROR_WRONG_DISK: The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1.
36 ERROR_SHARING_BUFFER_EXCEEDED: Too many files opened for sharing.
38 ERROR_HANDLE_EOF: Reached the end of the file.
39 ERROR_HANDLE_DISK_FULL: The disk is full.
50 ERROR_NOT_SUPPORTED: The request is not supported.
51 ERROR_REM_NOT_LIST: Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.
52 ERROR_DUP_NAME: You were not connected because a duplicate name exists on the network. Go to System in the Control Panel to change the computer name and try again.
53 ERROR_BAD_NETPATH: The network path was not found.
54 ERROR_NETWORK_BUSY: The network is busy.
55 ERROR_DEV_NOT_EXIST: The specified network resource or device is no longer available.
56 ERROR_TOO_MANY_CMDS: The network BIOS command limit has been reached.
57 ERROR_ADAP_HDW_ERR: A network adapter hardware error occurred.
58 ERROR_BAD_NET_RESP: The specified server cannot perform the requested operation.
59 ERROR_UNEXP_NET_ERR: An unexpected network error occurred.
60 ERROR_BAD_REM_ADAP: The remote adapter is not compatible.
61 ERROR_PRINTQ_FULL: The printer queue is full.
62 ERROR_NO_SPOOL_SPACE: Space to store the file waiting to be printed is not available on the server.
63 ERROR_PRINT_CANCELLED: Your file waiting to be printed was deleted.
64 ERROR_NETNAME_DELETED: The specified network name is no longer available.
65 ERROR_NETWORK_ACCESS_DENIED: Network access is denied.
66 ERROR_BAD_DEV_TYPE: The network resource type is not correct.
67 ERROR_BAD_NET_NAME: The network name cannot be found.
68 ERROR_TOO_MANY_NAMES: The name limit for the local computer network adapter card was exceeded.
69 ERROR_TOO_MANY_SESS: The network BIOS session limit was exceeded.
70 ERROR_SHARING_PAUSED: The remote server has been paused or is in the process of being started.
71 ERROR_REQ_NOT_ACCEP: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
72 ERROR_REDIR_PAUSED: The specified printer or disk device has been paused.
80 ERROR_FILE_EXISTS: The file exists.
82 ERROR_CANNOT_MAKE: The directory or file cannot be created.
83 ERROR_FAIL_I24: Fail on INT 24.
84 ERROR_OUT_OF_STRUCTURES: Storage to process this request is not available.
85 ERROR_ALREADY_ASSIGNED: The local device name is already in use.
86 ERROR_INVALID_PASSWORD: The specified network password is not correct.
87 ERROR_INVALID_PARAMETER: The parameter is incorrect.
88 ERROR_NET_WRITE_FAULT: A write fault occurred on the network.
89 ERROR_NO_PROC_SLOTS: The system cannot start another process at this time.
100 ERROR_TOO_MANY_SEMAPHORES: Cannot create another system semaphore.
101 ERROR_EXCL_SEM_ALREADY_OWNED: The exclusive semaphore is owned by another process.
102 ERROR_SEM_IS_SET: The semaphore is set and cannot be closed.
103 ERROR_TOO_MANY_SEM_REQUESTS: The semaphore cannot be set again.
104 ERROR_INVALID_AT_INTERRUPT_TIME: Cannot request exclusive semaphores at interrupt time.
105 ERROR_SEM_OWNER_DIED: The previous ownership of this semaphore has ended.
106 ERROR_SEM_USER_LIMIT: Insert the diskette for drive %1.
107 ERROR_DISK_CHANGE: The program stopped because an alternate diskette was not inserted.
108 ERROR_DRIVE_LOCKED: The disk is in use or locked by another process.
109 ERROR_BROKEN_PIPE: The pipe has been ended.
110 ERROR_OPEN_FAILED: The system cannot open the device or file specified.
111 ERROR_BUFFER_OVERFLOW: The file name is too long.
112 ERROR_DISK_FULL: There is not enough space on the disk.
113 ERROR_NO_MORE_SEARCH_HANDLES: No more internal file identifiers available.
114 ERROR_INVALID_TARGET_HANDLE: The target internal file identifier is incorrect.
117 ERROR_INVALID_CATEGORY: The IOCTL call made by the application program is not correct.
118 ERROR_INVALID_VERIFY_SWITCH: The verify-on-write switch parameter value is not correct.
119 ERROR_BAD_DRIVER_LEVEL: The system does not support the command requested.
120 ERROR_CALL_NOT_IMPLEMENTED: This function is not supported on this system.
121 ERROR_SEM_TIMEOUT: The semaphore timeout period has expired.
122 ERROR_INSUFFICIENT_BUFFER: The data area passed to a system call is too small.
123 ERROR_INVALID_NAME: The filename, directory name, or volume label syntax is incorrect.
124 ERROR_INVALID_LEVEL: The system call level is not correct.
125 ERROR_NO_VOLUME_LABEL: The disk has no volume label.
126 ERROR_MOD_NOT_FOUND: The specified module could not be found.
127 ERROR_PROC_NOT_FOUND: The specified procedure could not be found.
128 ERROR_WAIT_NO_CHILDREN: There are no child processes to wait for.
129 ERROR_CHILD_NOT_COMPLETE: The %1 application cannot be run in Win32 mode.
130 ERROR_DIRECT_ACCESS_HANDLE: Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.
131 ERROR_NEGATIVE_SEEK: An attempt was made to move the file pointer before the beginning of the file.
132 ERROR_SEEK_ON_DEVICE: The file pointer cannot be set on the specified device or file.
133 ERROR_IS_JOIN_TARGET: A JOIN or SUBST command cannot be used for a drive that contains previously joined drives.
134 ERROR_IS_JOINED: An attempt was made to use a JOIN or SUBST command on a drive that has already been joined.
135 ERROR_IS_SUBSTED: An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted.
136 ERROR_NOT_JOINED: The system tried to delete the JOIN of a drive that is not joined.
137 ERROR_NOT_SUBSTED: The system tried to delete the substitution of a drive that is not substituted.
138 ERROR_JOIN_TO_JOIN: The system tried to join a drive to a directory on a joined drive.
139 ERROR_SUBST_TO_SUBST: The system tried to substitute a drive to a directory on a substituted drive.
140 ERROR_JOIN_TO_SUBST: The system tried to join a drive to a directory on a substituted drive.
141 ERROR_SUBST_TO_JOIN: The system tried to SUBST a drive to a directory on a joined drive.
142 ERROR_BUSY_DRIVE: The system cannot perform a JOIN or SUBST at this time.
143 ERROR_SAME_DRIVE: The system cannot join or substitute a drive to or for a directory on the same drive.
144 ERROR_DIR_NOT_ROOT: The directory is not a subdirectory of the root directory.
145 ERROR_DIR_NOT_EMPTY: The directory is not empty.
146 ERROR_IS_SUBST_PATH: The path specified is being used in a substitute.
147 ERROR_IS_JOIN_PATH: Not enough resources are available to process this command.
148 ERROR_PATH_BUSY: The path specified cannot be used at this time.
149 ERROR_IS_SUBST_TARGET: An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute.
150 ERROR_SYSTEM_TRACE: System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.
151 ERROR_INVALID_EVENT_COUNT: The number of specified semaphore events for DosMuxSemWait is not correct.
152 ERROR_TOO_MANY_MUXWAITERS: DosMuxSemWait did not execute; too many semaphores are already set.
153 ERROR_INVALID_LIST_FORMAT: The DosMuxSemWait list is not correct.
154 ERROR_LABEL_TOO_LONG: The volume label you entered exceeds the label character limit of the target file system.
155 ERROR_TOO_MANY_TCBS: Cannot create another thread.
156 ERROR_SIGNAL_REFUSED: The recipient process has refused the signal.
157 ERROR_DISCARDED: The segment is already discarded and cannot be locked.
158 ERROR_NOT_LOCKED: The segment is already unlocked.
159 ERROR_BAD_THREADID_ADDR: The address for the thread ID is not correct.
160 ERROR_BAD_ARGUMENTS: The argument string passed to DosExecPgm is not correct.
161 ERROR_BAD_PATHNAME: The specified path is invalid.
162 ERROR_SIGNAL_PENDING: A signal is already pending.
164 ERROR_MAX_THRDS_REACHED: No more threads can be created in the system.
167 ERROR_LOCK_FAILED: Unable to lock a region of a file.
170 ERROR_BUSY: The requested resource is in use.
173 ERROR_CANCEL_VIOLATION: A lock request was not outstanding for the supplied cancel region.
174 ERROR_ATOMIC_LOCKS_NOT_SUPPORTED: The file system does not support atomic changes to the lock type.
180 ERROR_INVALID_SEGMENT_NUMBER: The system detected a segment number that was not correct.
182 ERROR_INVALID_ORDINAL: The operating system cannot run %1.
183 ERROR_ALREADY_EXISTS: Cannot create a file when that file already exists.
186 ERROR_INVALID_FLAG_NUMBER: The flag passed is not correct.
187 ERROR_SEM_NOT_FOUND: The specified system semaphore name was not found.
188 ERROR_INVALID_STARTING_CODESEG: The operating system cannot run %1.
189 ERROR_INVALID_STACKSEG: The operating system cannot run %1.
190 ERROR_INVALID_MODULETYPE: The operating system cannot run %1.
191 ERROR_INVALID_EXE_SIGNATURE: Cannot run %1 in Win32 mode.
192 ERROR_EXE_MARKED_INVALID: The operating system cannot run %1.
193 ERROR_BAD_EXE_FORMAT: %1 is not a valid Win32 application.
194 ERROR_ITERATED_DATA_EXCEEDS_64k: The operating system cannot run %1.
195 ERROR_INVALID_MINALLOCSIZE: The operating system cannot run %1.
196 ERROR_DYNLINK_FROM_INVALID_RING: The operating system cannot run this application program.
197 ERROR_IOPL_NOT_ENABLED: The operating system is not presently configured to run this application.
198 ERROR_INVALID_SEGDPL: The operating system cannot run %1.
199 ERROR_AUTODATASEG_EXCEEDS_64k: The operating system cannot run this application program.
200 ERROR_RING2SEG_MUST_BE_MOVABLE: The code segment cannot be greater than or equal to 64K.
201 ERROR_RELOC_CHAIN_XEEDS_SEGLIM: The operating system cannot run %1.
202 ERROR_INFLOOP_IN_RELOC_CHAIN: The operating system cannot run %1.
203 ERROR_ENVVAR_NOT_FOUND: The system could not find the environment option that was entered.
205 ERROR_NO_SIGNAL_SENT: No process in the command subtree has a signal handler.
206 ERROR_FILENAME_EXCED_RANGE: The filename or extension is too long.
207 ERROR_RING2_STACK_IN_USE: The ring 2 stack is in use.
208 ERROR_META_EXPANSION_TOO_LONG: The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
209 ERROR_INVALID_SIGNAL_NUMBER: The signal being posted is not correct.
210 ERROR_THREAD_1_INACTIVE: The signal handler cannot be set.
212 ERROR_LOCKED: The segment is locked and cannot be reallocated.
214 ERROR_TOO_MANY_MODULES: Too many dynamic-link modules are attached to this program or dynamic-link module.
215 ERROR_NESTING_NOT_ALLOWED: Cannot nest calls to LoadModule.
216 ERROR_EXE_MACHINE_TYPE_MISMATCH: The image file %1 is valid, but is for a machine type other than the current machine.
230 ERROR_BAD_PIPE: The pipe state is invalid.
231 ERROR_PIPE_BUSY: All pipe instances are busy.
232 ERROR_NO_DATA: The pipe is being closed.
233 ERROR_PIPE_NOT_CONNECTED: No process is on the other end of the pipe.
234 ERROR_MORE_DATA: More data is available.
240 ERROR_VC_DISCONNECTED: The session was canceled.
254 ERROR_INVALID_EA_NAME: The specified extended attribute name was invalid.
255 ERROR_EA_LIST_INCONSISTENT: The extended attributes are inconsistent.
258 WAIT_TIMEOUT: The wait operation timed out.
259 ERROR_NO_MORE_ITEMS: No more data is available.
266 ERROR_CANNOT_COPY: The copy functions cannot be used.
267 ERROR_DIRECTORY: The directory name is invalid.
275 ERROR_EAS_DIDNT_FIT: The extended attributes did not fit in the buffer.
276 ERROR_EA_FILE_CORRUPT: The extended attribute file on the mounted file system is corrupt.
277 ERROR_EA_TABLE_FULL: The extended attribute table file is full.
278 ERROR_INVALID_EA_HANDLE: The specified extended attribute handle is invalid.
282 ERROR_EAS_NOT_SUPPORTED: The mounted file system does not support extended attributes.
288 ERROR_NOT_OWNER: Attempt to release mutex not owned by caller.
298 ERROR_TOO_MANY_POSTS: Too many posts were made to a semaphore.
299 ERROR_PARTIAL_COPY: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
300 ERROR_OPLOCK_NOT_GRANTED: The oplock request is denied.
301 ERROR_INVALID_OPLOCK_PROTOCOL: An invalid oplock acknowledgment was received by the system.
302 ERROR_DISK_TOO_FRAGMENTED: The volume is too fragmented to complete this operation.
303 ERROR_DELETE_PENDING: The file cannot be opened because it is in the process of being deleted.
317 ERROR_MR_MID_NOT_FOUND: The system cannot find message text for message number 0x%1 in the message file for %2.
487 ERROR_INVALID_ADDRESS: Attempt to access invalid address.
534 ERROR_ARITHMETIC_OVERFLOW: Arithmetic result exceeded 32 bits.
535 ERROR_PIPE_CONNECTED: There is a process on other end of the pipe.
536 ERROR_PIPE_LISTENING: Waiting for a process to open the other end of the pipe.
994 ERROR_EA_ACCESS_DENIED: Access to the extended attribute was denied.
995 ERROR_OPERATION_ABORTED: The I/O operation has been aborted because of either a thread exit or an application request.
996 ERROR_IO_INCOMPLETE: Overlapped I/O event is not in a signaled state.
997 ERROR_IO_PENDING: Overlapped I/O operation is in progress.
998 ERROR_NOACCESS: Invalid access to memory location.
999 ERROR_SWAPERROR: Error performing inpage operation.
1001 ERROR_STACK_OVERFLOW: Recursion too deep; the stack overflowed.
1002 ERROR_INVALID_MESSAGE: The window cannot act on the sent message.
1003 ERROR_CAN_NOT_COMPLETE: Cannot complete this function.
1004 ERROR_INVALID_FLAGS: Invalid flags.
1005 ERROR_UNRECOGNIZED_VOLUME: The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted.
1006 ERROR_FILE_INVALID: The volume for a file has been externally altered so that the opened file is no longer valid.
1007 ERROR_FULLSCREEN_MODE: The requested operation cannot be performed in full-screen mode.
1008 ERROR_NO_TOKEN: An attempt was made to reference a token that does not exist.
1009 ERROR_BADDB: The configuration registry database is corrupt.
1010 ERROR_BADKEY: The configuration registry key is invalid.
1011 ERROR_CANTOPEN: The configuration registry key could not be opened.
1012 ERROR_CANTREAD: The configuration registry key could not be read.
1013 ERROR_CANTWRITE: The configuration registry key could not be written.
1014 ERROR_REGISTRY_RECOVERED: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.
1015 ERROR_REGISTRY_CORRUPT: The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was abs
1016 ERROR_REGISTRY_IO_FAILED: An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.
1017 ERROR_NOT_REGISTRY_FILE: The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.
1018 ERROR_KEY_DELETED: Illegal operation attempted on a registry key that has been marked for deletion.
1019 ERROR_NO_LOG_SPACE: System could not allocate the required space in a registry log.
1020 ERROR_KEY_HAS_CHILDREN: Cannot create a symbolic link in a registry key that already has subkeys or values.
1021 ERROR_CHILD_MUST_BE_VOLATILE: Cannot create a stable subkey under a volatile parent key.
1022 ERROR_NOTIFY_ENUM_DIR: A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.
1051 ERROR_DEPENDENT_SERVICES_RUNNING: A stop control has been sent to a service that other running services are dependent on.
1052 ERROR_INVALID_SERVICE_CONTROL: The requested control is not valid for this service.
1053 ERROR_SERVICE_REQUEST_TIMEOUT: The service did not respond to the start or control request in a timely fashion.
1054 ERROR_SERVICE_NO_THREAD: A thread could not be created for the service.
1055 ERROR_SERVICE_DATABASE_LOCKED: The service database is locked.
1056 ERROR_SERVICE_ALREADY_RUNNING: An instance of the service is already running.
1057 ERROR_INVALID_SERVICE_ACCOUNT: The account name is invalid or does not exist, or the password is invalid for the account name specified.
1058 ERROR_SERVICE_DISABLED: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
1059 ERROR_CIRCULAR_DEPENDENCY: Circular service dependency was specified.
1060 ERROR_SERVICE_DOES_NOT_EXIST: The specified service does not exist as an installed service.
1061 ERROR_SERVICE_CANNOT_ACCEPT_CTRL: The service cannot accept control messages at this time.
1062 ERROR_SERVICE_NOT_ACTIVE: The service has not been started.
1063 ERROR_FAILED_SERVICE_CONTROLLER_CONNECT: The service process could not connect to the service controller.
1064 ERROR_EXCEPTION_IN_SERVICE: An exception occurred in the service when handling the control request.