Identifying problems when reinstalling Windows. Three reasons to reinstall Windows. Installing the incorrect OS version

Windows installs and adapts itself to a specific hardware. With a modest addition of RAM, a change in processor or video card, the built-in OS mechanisms will independently reconfigure Windows. But with a deeper upgrade (change of platform, motherboard, several components at once), the operating system most often does not want to boot even in safe mode.

A direct analogy is a person who somehow woke up in a completely unfamiliar place. So is Windows, which “woke up” in an unknown environment. Only the installation disk will help - and some sleight of hand so as not to lose old data, settings and files.

Reason 2: switching to another OS version

Precisely to a different one, and not just to a more recent one. The newfangled “ten” is not suitable for everyone, especially the categorically unusual “eight”. Formally, Microsoft operating systems have supported updating on top of themselves since Vista, but not in the case of rolling back to an older version. And there is a high probability of getting glitches and slowdowns from the old OS. Experienced users are convinced that the new version should be truly new, without problems at the hereditary level. And this is only possible when installing Windows from scratch.

Reason 3: something rare, unknown, or extremely harmful

The volume of Windows software code has been measured in gigabytes for several generations. Developers try to debug everything possible; many problems are solved by the collective intelligence of billions of users around the planet. But rare oddities that cannot be treated are also inevitable. The author of this article has encountered such unidentified Windows objects as:

• complete refusal of the OS to install any drivers. In that case, there was an endless message “Please wait, the driver is being installed” when connecting even a banal flash drive or mouse. Everything else worked perfectly, but there was little joy from it.
• malware attack. Normal situation: the antivirus works, independently treats the infected area, asks to reboot... and that’s it. Neither connecting the hard drive to another PC, nor attempts at treatment with LiveCD utilities, nor dozens of attempts to resurrect the suddenly deceased Windows helped.

And when you can’t do without reinstallation, well, there is always room for change in life; the main thing is to have regular backups and an installation disk at hand.

I can't install Windows 7! Inexperienced users often encounter this problem and go to the Internet in search of a solution.

And rightly so, because our material will really help you get rid of a number of possible problems.

To make it easier to determine the “culprit” of installation problems, we will group these objects into several general categories:

• installation image – OS installation files;
• installation image media – CD, DVD or USB FLASH disk;
• image carrier reader;
• BIOS of the computer on which the OS is installed;
• computer hard drive;
• computer equipment;
• computer peripheral devices.

When an error occurs, you need to check the groups one by one, narrowing the search for the faulty category, the cause of the fault, and how to solve the problem.

Nowadays, reinstalling the operating system is more often done using a USB FLASH than from a DVD.

This installation requires preparation of both the media and special BOIS settings on the computer.

Preparing a flash drive involves deploying a bootable installation image on it. The following programs are useful for this: UltraISO, WinSetupFromUSB, etc.

Often errors when installing from a flash drive are associated with incorrect deployment of the image.

Case 1. If you can’t install Windows 7 from a flash drive

• We check the functionality of the flash drive - connect it to a working computer, try to copy and write several files. We check the disk using standard means (right-click – Properties – Tools – Run check);
• We try to boot the computer from a flash drive by inserting it into the rear connectors. There are long wires stretching from the front USB connectors, which can cause interference that distorts the data read from the media.
  A telltale sign of a problem is that the installation is interrupted by an error at an unpredictable point during the process.
• we check whether . Having connected the flash drive to the computer, we enter the interface. Its name should appear among other hard drives.
  If this does not happen, then you need to use another flash drive. The flash drive is detected normally, then we try to prepare it with other programs, use other installation images.

Case 2. If you can’t install Windows 7 via BIOS

In this case, we proceed in the same sequence as in case of problems with a flash drive: is the media working, is the reading device working correctly, is the image deployed on the media working.

If the problem is due to the fact that you cannot get into the BIOS settings window, then we try to set the boot device when turning on the computer using the function keys.

As a rule, the “Boot device selection” function is activated by the F8, F11, F12 or ESC button, via the selection menu.

It is important not to miss the moment and press the button immediately after turning on the computer.

This function can also be used to check whether the USB flash drive is detected by the system.

Case 3. If you can’t install Windows 7, the driver is not found

The probable cause is a hard drive or media that is not supported by standard means. The problem has become especially relevant with the spread of USB 3.0.

The Windows 7 distribution does not support USB 3.0 by default.

Therefore, you need to stock up on drivers or use a non-original image for installation, in which these are already present.

You can find and download a suitable image by searching for “Windows 7 USB 3.0”. When this error is detected, the system provides the opportunity to install the necessary drivers.

Important! If the installation was carried out from a flash drive, then you need to move the flash drive from the USB 3.0 connector (blue core) to USB 2.0 (black core) or disable USB 3.0 support through the BIOS interface.

If the flash drive from which you are installing the operating system is in USB 3.0 format, then you need to disable the USB XHCI Controller option in the BIOS, and enable AHCI mode for hard drives.

Another reason for the missing driver error is an outdated BIOS version.

Updating the BIOS program helps overcome the problem. The problem is that the outdated BIOS does not contain instructions for working with large media.

This means that you need a shortened (stripped down) installation image and media with a small amount of memory.

There are cases when a driver search error was associated with minor mechanical damage to the optical media - a DVD disc.

The problem can be solved by recording the installation image onto a working medium.

A drive with a dead laser does not read all disks and may make a reading error in a critical block of installation data.

After upgrading your computer hardware, sometimes the system installation fails due to insufficient power from the power supply.

The problem manifests itself in spontaneous system reboots during installation or prolonged irreversible freezes.

The widely and infamous Blue Screen of Death will invariably occur when attempting to install Windows if there are corrupt cells in the computer's RAM.

The only way to solve the problem is to replace the faulty RAM module.

Peripheral devices attached to the computer may affect installation in unexpected ways.

Therefore, before starting the installation, you need to disconnect everything except the mouse and keyboard.

Installing Windows 7 from a USB flash drive on a computer and laptop

I can’t install windows 7: how to solve basic errors

Many users, when serious problems occur in Windows XP, prefer “amputation”: formatting the disk and completely reinstalling the OS. However, such a simple and radical surgical method is not suitable if the system has many important programs installed and configured, the reinstallation of which is impossible or would be too expensive. In this case, an in-depth diagnostic of Windows is required.

Each type of Windows XP failure has its own cause, and therefore, although there are quite clear recipes for getting rid of the most common problems, it is impossible to develop any universal “treatment” method to eliminate most “glitches”. The configuration of each operating system, software, drivers and hardware is unique, and most often it is possible to find out the cause of the problem only by carefully dissecting the hardware and software inside of a particular computer. If the failure does not accompany the OS right from the moment of its installation, but appeared at some specific moment (after installing another program or driver, changing Windows settings, power failure), then it is easy to get rid of it, just remove the problematic application, or restore the registry or even the entire contents of the hard drive from a backup. Not only the standard System Restore will help with this, but also more interesting programs, for example, Norton Ghost, Ashampoo Uninstaller, WinRescue XP. Of course, this is possible if the user does not disdain prevention and regularly uses such programs, which is not at all difficult, by the way. For example, a full backup of a 10 GB system NTFS partition in Norton Ghost takes only 10 minutes (it is unreasonable to allocate the entire disk space to the OS).

If it is not possible to either restore the system with little effort or completely reinstall it, then you will have to look for the cause of the failure yourself. To achieve success in such a thankless and tedious task, it is recommended to follow the following technology:

Preliminary stage

1. Before starting diagnostics, make a backup copy of the registry, configuration files, or the entire system, so as not to get even bigger problems as a result of experiments. Be sure to remember all your further actions so that in case of problems you can easily cancel them.
2. Delete all temporary files, clear the browser cache, Recycle Bin, Journal, empty the Program Files\ Internet Explorer\ Plugins folder with IE plugins (make backup copies to restore them). Clear the folders from which MS-Office scripts autorun (such as Documents and Settings\ USER\ Application Data\ Microsoft\ Excel\ Xlstart, Documents and Settings\ USER\ Application Data\ Microsoft\ Word\ Startup), delete the normal.dot template, used by MS-Office. Empty the Windows folders\ Downloaded Program Files, Documents and Settings\ USER\ NetHood, Documents and Settings\ USER\ PrintHood, Documents and Settings\ USER\ Recent. Remove autorun.inf files from all local drives.
3. Check the system with several recent antiviruses and the Ad-Aware program, scan the hard drive with utilities such as ScanDisk, Norton DiskDoctor (with the mandatory inclusion of write testing). Check system files using the System File Checker utility (SFC /SCANNOW command) and restore damaged libraries from the Windows distribution or Service Pack.
4. Update the system: in addition to the latest service pack (if it is already installed, reinstall it) install all the latest patches on the Windows Update website (windowsupdate.microsoft.com, just keep in mind that some patches themselves can be a source of problems). Update (reinstall) Internet Explorer and the JAVA virtual machine from Microsoft. Update DirectX using the redist distribution (about 25-30 megabytes in size, and the file name contains the word “REDIST”: DX90b_Redist.exe). Sometimes it is useful to first remove Internet Explorer or DirectX, and then install it again - for this you can use the XPLite utility.

Search for a ready-made solution

1. Carefully study the documentation for the faulty program or expansion card; perhaps it contains some special instructions. Also visit the website of the developer of the faulty program or device - perhaps the manufacturer's technical support service knows about the problem and offers to download a patch.
2. If the failure is accompanied by error messages (for example, STOP errors on a blue screen), then write down their exact contents and go to the Microsoft support site. Based on the error message, you need to formulate a query for the search engine (for maximum search efficiency, try formulating the query in several different ways). Finding a solution in the Microsoft database is the fastest way to resolve the problem. If there is no information about your failure in the Microsoft database, then run a specialized Internet search utility, for example, Copernic or Search Plus, and also try to find materials on similar problems on the Internet and in UseNet technical conferences. Or use Russian and foreign search engines such as Yandex, Yahoo or Google.
3. Just keep in mind that if your system has automatic reboot mode enabled in case of failures, the “blue screen of death” message will not be displayed. Therefore, in the menu Control Panel - System - Startup and Recovery - Settings, uncheck the Automatically restart flag in advance.
4. To obtain maximum information about the failure that occurred, also refer to the system error log - Event Log (Computer Management - Event Viewer, “Computer Management” - “Event Viewer”). Documentation for most Event ID event codes is available on the Microsoft Events and Errors Message Center and www.eventid.net websites. Something can be squeezed out of the Dr.Watson system debugger, which can be called from the System Information program window.
5. In Windows XP, enable error reporting mode to Microsoft: Control Panel → System → Advanced → Error reporting → Enable Error Reporting (Control Panel → System → Advanced → Error Report → Enable Error Reporting). You will laugh, but there have been cases when, after sending information about a failure to the developers, the user received a response with a specific solution to the problem.
6. Check out sites dedicated to the nation's efforts to combat Windows crashes, such as www.techadvice.com, www.jsiinc.com/reghack.htm, www.mdgx.com, www.aumha.org, labmice.techtarget.com/troubleshooting/generalguides .htm - on them you will find links to articles devoted to troubleshooting many common failures.
7. Visit popular web and UseNet conferences on operating systems, software and computer hardware. Having formulated a description of the failure of your system in extreme detail (and not forgetting to indicate its version!), indicating the exact content of the error message and describing the configuration of your system, try asking for help from other users - perhaps someone has already encountered a similar problem and knows its solution, or may suggest the direction of further searches.

Checking settings

1. In the Control Panel, check all system and hardware settings - set all parameters to the “Default” position. Specifically, remove page file size limits, check that you have enough disk space, and temporarily set your environment variable settings to a shorter path to the TEMP folder (for example, C:\TEMP). Even in your keyboard settings, set the default language to English. Also check all settings in the options of the applications you use.
2. Return the settings in the registry and in the configuration files user.ini, system.ini made using tweaking utilities to their original state. Check the settings in the files autoexec.nt, config.nt, _default.pif. Run a search in the registry for the word “Policies” and delete all parameters in the found sections (except for the PowerCfg sections responsible for power policies, as well as the HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ Internet Settings\ TemplatePolicies section, which contains IE security policy templates) - Perhaps the failure is just a consequence of restricting user rights. Carefully check your current security policy settings in the Group Policy Editor (GPEDIT.MSC).
3. Return the settings in the BIOS to the original - Default - state, experiment with different CMOS Setup options, for example, disable DMA mode for disks, change memory timings, disable all integrated devices, enable the “hole” in the region of 15 megabytes of memory. Disable everything related to power management in CMOS Setup, including ACPI. Or vice versa - enable all these options if they are disabled. Similarly, experiment with the PnP OS Installed and USB Legacy Support option. Update your BIOS. And give up overclocking: overclocking is the main enemy of Windows XP!

System and programs

1. Run the msconfig.exe utility and disable all startup programs. Try also experimenting with the Selective Startup mode - perhaps the incorrect entry is hidden in system.ini or win.ini, another rudimentary configuration file. Using msconfig, it is convenient to check system services, for example, by comparing the list of running services with another PC on which a similar failure is not observed. A good description of the purpose of Windows XP services, which will help you find out the initial and recommended status of their configuration in different versions of Windows, can be found at www.blackviper.com. Try disabling unnecessary services, for example, WEB Client, and also check service dependencies using the Services snap-in.
2. Try to remember after what actions the failure appeared. Uninstall several programs and drivers that were most recently installed - perhaps one of them is causing the system to crash or conflicts with other programs and hardware, causing them to crash. Uninstall any programs that were created more than two years ago and have not been updated since then. Remove antiviruses and other software that closely integrates with the system. Be sure to use a specialized uninstaller like Ashampoo Uninstaller, both when installing and uninstalling programs - this is the only way to completely clear the system of all traces of the program or driver being removed! In addition, analysis of the uninstaller log allows you to find out which files on the disk and which parameters in the registry were changed during the installation of the program - often to eliminate the failure it is enough to change the incorrectly changed parameter in the registry. When reinstalling programs and drivers, try not only the latest version (note that some programs are regularly updated with patches), but also the older one - it often turns out to be more stable. Try reinstalling the failed application in a different directory with a shorter name.
3. For outdated programs, try installing a special compatibility mode. To do this, create a shortcut to the program, go to its properties and on the “Compatibility” tab, in the “Run in emulation mode” item, select the compatibility mode with another type of Windows. In addition, use the Application Compatibility Toolkit, which is designed to significantly expand the capabilities and manual configuration of this mode.
4. Try running the failed application under an administrator account. If the program runs only under it, then from the Administrator account, find the section with the settings of the desired program in the HKEY_LOCAL_MACHINE\ SOFTWARE registry branch and right-click on it. Select the “Permissions” command from the menu that appears and set full access to this registry branch for the user or group of users who are allowed to work with it. Also find in the HKEY_CURRENT_USER branch the section corresponding to the faulty program and export it to a REG file. Now log in as a regular user and import this REG file back into the registry. Sometimes you can get rid of such a failure by deleting your account (and your entire user profile) and then creating it again.
5. Try finding and fixing errors in the registry using a program like Norton WinDoctor. Errors found should be corrected only manually, analyzing each of them. To do this, you need to try to find out which program or system setting the erroneous registry entry relates to by looking in RegEdit at the branch that WinDoctor signals - using the names of files, parameters, or the specified paths, it is easy to install the application that generated the error. Try using other diagnostic utilities, for example, the DirectX Diagnostic Tool included in Windows; it will check DirectX files, drivers, and settings of some devices. Some simple glitches can be fixed by the Tweak UI program; it has a “Repair” tab for this purpose.
6. Some Windows XP problems can be resolved by restoring the hard disk's master boot record (MBR) using the "fdisk /mbr" command after starting the PC from a Windows 98 floppy disk (this is necessary to subsequently overwrite the disk ID), or by using the recovery console commands "fixboot" and "fixmbr" " Boot your PC from a Windows 98/Me NTFS-enabled floppy disk (use NTFS for DOS Pro to do this) or ERD Commander disk and delete the PAGEFILE.SYS file. ERD Commander, generally speaking, is an excellent program that is a kind of LiveCD for Windows XP. It allows you to fix many problems and access OS settings, even if Windows itself does not boot into crash protection mode. Check for errors in boot.ini and current access rights to files and folders: the “System” and “Administrators” user group must have full access rights to the root directory of the system drive and to the virtual memory file PAGEFILE.SYS.
7. At the moment of a failure, monitor various system events, queries and registry accesses using special monitoring programs. By analyzing access to the registry, you can, for example, determine which parameters from the registry are requested by the program immediately at the time of a failure - perhaps some of them are missing or have an incorrect value. And by analyzing access to files, it is easy to understand which files contain the settings of the faulty program, and which files it needs are missing. Utilities from SysInternals will help with this: Registry Monitor - analysis of accesses to the registry, File Monitor - monitoring of access to files, DllView - information about libraries used by current processes, OpenList - information about all open files, PortMon - access to ports, TCPView - information about connections via the TCP protocol. The TaskInfo program is best at displaying information about all running programs. It will also show how much CPU resources each application consumes. You can find out the cause of the jam that occurs during boot using the well-known diagnostic utility BootVis (however, Microsoft no longer distributes it, so use the search). Also check the system with a comprehensive diagnostic and information package SiSoft Sandra or AIDA32.
8. Remove unnecessary fonts, disable all performance counters, make sure that there are no folders or files on the disk with very long names or extensions (220 characters or more), do not use very long command line parameters (220 characters or more) when working with programs.

Equipment

1. Update all drivers for all devices (or remove and reinstall the drivers of the problematic device, as well as the driver of the device to which it is connected), especially the chipset drivers: Intel Chipset Software Installation Utility and Intel Application Accelerator or VIA-4-in-1 ( plus other drivers and patches from VIA, such as VIA IRQ Routing Miniport Driver, VIA IDE Miniport driver and others, depending on the system configuration). Check for special patches and updates on the websites of equipment manufacturers, and most importantly, the motherboard.
2. Check the serviceability of the equipment, the correct installation of jumpers on it, test it using utilities such as Memory Test, CPU Stability Test and the like. Check everything, right down to the battery, power supply voltage and the quality of the motherboard fastening - there should be no spontaneous short circuits or unreliable contacts anywhere!
3. Temporarily replace all memory modules - this is the device that fails most often. If this is not possible, then try limiting its size, for example, to the first 64 megabytes. In Windows XP, it is convenient to use the MSCONFIG.EXE utility for this: the MAXMEM parameter in the boot.ini file. Try a more powerful power supply, oddly enough, lack of power is very often the cause of Windows crashes.
4. Check the temperature and functionality of the cooling devices of all system components, even the chipset (you can even install a special fan on the chipset heatsink). Ground the PC, install a surge protector or an uninterruptible power supply. Check the quality of the telephone cable, network cable, electrical wiring.
5. Remove all additional devices from the PC (except the hard drive and video card, although sometimes replacing the video card helps), even the internal tweeter, and then in crash protection mode, using the “System Properties” dialog, remove them drivers and see if the problem is gone. If it disappears, then install the devices back one by one, each time repeating the procedure, which usually leads to an error message - perhaps there is some kind of hardware conflict and in this way you will either identify its source, or the system will re-allocate resources and eliminate it itself .
6. Install the problematic device in another PCI slot, in the system properties and the System Information utility (Program Files\ Common Files\ Microsoft Shared\ MSInfo\ msinfo32.exe) check for no conflicts. The SiSoftware Sandra program is very good for obtaining information about the system. If ACPI is disabled, try manually reassigning conflicting interrupts (or other resources, such as DMA channels or I/O ranges). Try replacing the problematic device with exactly the same one, or with a device of a different brand - perhaps a defective unit is simply to blame, or changing the manufacturer of the expansion board will eliminate the conflict. For disks, try a different cable, instead of an 80-wire cable, try a 40-wire cable and vice versa, check that the Master/Slave jumpers are set correctly, move the disk to another cable, set it in CMOS Setup to either auto-detection mode, or set its parameters explicitly, or set it to "NONE". Do not connect other devices to the same cable with the problem disk.
7. Look at the properties of the problematic device - perhaps there are settings there that will resolve the problem, for example, disable or enable DMA mode for the disk. If the computer does not boot, try accessing these menus from Safe Mode.
8. In case of problems with drivers, boot the PC in crash protection mode, in Device Manager, remove the problematic device (as well as all printers and devices that do not exist in reality, even joysticks) and after loading the OS in normal mode, install the latest driver. However, sometimes an older driver turns out to be more stable, try different versions. Please note that instead of rebooting, a failure can sometimes be resolved by completely turning off the PC and then turning it on after a few minutes of idle power. If the failure has something to do with the network, then in the Network properties, remove all network components and after rebooting, install everything necessary again. Remove all printers if there are problems with them, and also reinstall their drivers after rebooting. Remove all drivers that are not certified for Windows XP; the File Signature Verification utility, called from the System Information program window, will help you check the signatures of system files. If the driver was installed unsuccessfully, then use either loading the last known good configuration (called in the Windows boot menu), or roll back to the previous version of the driver in the system properties.

It's bad

1. Reinstalling Windows over a previous installation will restore all files to their original versions, but will retain the main settings in the registry, so if the cause of the failure is incorrect registry settings, then such a reinstallation may not fix anything. In some cases, immediately before installation, you can remove all hardware from the crash protection mode in the “System Properties” dialog so that Windows can reinstall all the drivers. Also try different OS distribution disks - the original disk may be damaged.
2. After completely erasing the Windows, Program Files, System Volume Information and Recycler folders (or repartitioning and formatting the disk), install Windows bare-bones. Perhaps Windows 2000 or Windows 98 will be more efficient. Sometimes you need to format the disk with a special utility from the hard drive manufacturer to completely reset it. In some cases, for example, after programs like Partition Magic work incorrectly, to fix the failure you need to partition the disk again using standard Fdisk.

Finish

Contact a specialist or... try your luck with Linux...

1. www.symantec.com
2. www.ashampoo.com
3. www.superwin.com
4. www.lavasoft.com
5. www.microsoft.com/windows/ie/download/default.htm
6. www.microsoft.com/java/vm/dl_vm40.htm
7. www.litepc.com
8. search.support.microsoft.com/search/?adv=1
9. www.copernic.com
10. srchplus.chat.ru
11. www.microsoft.com/technet/support/ee/ee_advanced.aspx
12. www.eventid.net
13. www.techadvice.com
14. www.jsifaq.com/reghack.htm
15. www.mdgx.com
16. www.aumha.org
17. labmice.techtarget.com/troubleshooting/generalguides.htm
18. www.blackviper.com
19. www.microsoft.com/windows/appcompatibility/default.mspx
20. www.winternals.com
21. www.sysinternals.com
22. www.iarsn.com
23. www.microsoft.com/whdc/hwdev/platform/performance/fastboot/BootVis.mspx
24. sisoftware.net
25. www.aida32.hu/aida32.php
26. support.intel.com/support/chipsets/driver.htm
27. www.viaarena.com/?PageID=66

Any Windows-based operating system crashes after a long period of use. System disks become clogged with residual and temporary files and programs. Disorder in the system leads to a decrease in overall productivity. The device takes a long time to load and performs operations slowly. The biggest problem for users is the occurrence of errors due to failures in Windows 7. There are internal and external ways to resolve errors in the system. Internal methods involve the use of Windows power and resources; external methods use programs and utilities.

Checking the disk using CHKDSK

CHKDSK is a utility utility built into the operating system. The purpose of the utility is to restore damaged sectors on the hard drive. Also, CHKDSK fixes system file errors. The utility is launched from the command line in Windows 7. You can launch the command line in several ways:

• Keyboard shortcut Win+R;
• Start key, enter the query “cmd” in the search bar;
• Start key, Programs, Accessories, Command Prompt.

In the black window that opens, enter the command: “chkdsk C: /F”. Command meaning:

• Chkdsk – disk check;
• C: - name of the system drive, the letter may be different, a colon is required;
• /F – designation of the action; the system will automatically check itself for errors and eliminate them.

After entering the command, press the Enter button. At the next reboot, the system will check and correct errors.

Check with sfc scannow command

The utility can also be launched from the command line. To run the scan, you will need Administrator rights. At the command line you need to enter “sfc /scannow”. The system will automatically check files, including closed ones, correct errors, and restore damaged ones from a cached copy.

Standard diagnostics for Windows problems

Using the command line is suitable for advanced users. For those who are not well versed in how computers work, the windowed option for diagnosing and troubleshooting problems is suitable. Additionally, users of the Windows 7 operating system have access to tools for searching for solutions and downloading important updates in the Update and Support Centers.

Troubleshooting Control Panel

This is an internal Windows program that allows you to diagnose the system for errors and find solutions to eliminate them. You can launch it in the following way:

A window will open with a list of all system capabilities of the computer. In most cases, it is enough to run a check of the “Performance” item. By double clicking on the selected item, the user will start the scan. To ensure that the system fixes errors immediately, you should check the “Automatically apply fixes” checkbox.

Find solutions in the Support Center

The Action Center tool monitors the status of the operating system and stores reports of errors and failures. Using the Center, you can find problems that have occurred and correct them.

To correct errors in the system, go to the “Maintenance” section of the Center.

Checking for updates in the Update Center

Windows 7 is already considered outdated. Microsoft has stopped actively supporting users on this version of the operating system, but updates are still being released. Their installation is optional, but the system corrects errors and restores damaged files during the process of downloading the next update.

On newly installed Windows, updates are searched for and downloaded automatically. If this option is disabled, the user can start the process manually:

1. Click the Start button;
2. Enter the Control Panel, System and Security sections;
3. Select Windows Update;
4. On the left side of the window, click on “Search for updates”;
5. Wait for the procedure to complete.

The system will offer to install the found updates. It is recommended to agree.

Error correction programs

Many programs have been developed for Windows operating systems that can improve performance, fix errors, and remove registry errors. Such utilities are lightweight and do not take up computer resources.

Advanced System Care

The utility puts your computer in order in a comprehensive manner. Advanced System Care is distributed free of charge and can be downloaded from the developer’s website.

Important! When installing, you should carefully read the information provided and uncheck the boxes for installing additional adware.

After installing and launching Advanced System Care, a window with a simple interface will appear in front of the user. There are 2 modes of working with the utility, simplified and expert. In any of the modes, just press the large “Start” button. The utility will independently check the system for:

• Viruses;
• Erroneous entries in the registry;
• Temporary, residual, unwanted files;
• Network problems;
• Erroneous labels;
• Possible threats to privacy.

At the user's command, all threats or some of them will be removed.

CCleaner

One of the best programs for cleaning and fixing the registry for Windows operating systems. CCleaner is distributed free of charge. As in the previous case, it is recommended to carefully read the information in the installation windows. You can download CCleaner on the official website of the developer.

After starting the program, the user is presented with 2 menus. On the left side are the main functions, on the right are the launch of specific operations. Working with CCleaner takes place in 3 stages:

1. "Service" tab. Here is a list of all installed programs on your PC. They can be uninstalled. There are also tabs for startup, search for duplicate files, and analysis of system drives.
2. Registry tab. It is recommended to go to it after uninstalling programs. CCleaner will find all erroneous entries in the system and offer to correct or delete them.
3. Cleaning tab. The utility detects temporary files of the system and browsers and deletes them. This procedure allows you to clear space on the system disk.

The above steps will significantly improve PC performance. It is recommended to regularly analyze and clean using the Ccleaner utility.

Windows 7 Manager

The Windows 7 Manager utility allows you to carry out full maintenance of the operating system. You can download the software.

Windows 7 Manager works similarly to CCleaner, but gives the user access to advanced functionality for optimization, cleaning, networking and PC protection.

To find and fix errors in Windows 7, you should sequentially select items in the left menu, analyze and clean the system.

Microsoft Fix It

The software is designed specifically to work with Windows. The Microsoft Fix It utility is downloaded and installed for free. In the utility window, the user is offered a list of system tools, for each of which you can run an error check and subsequent correction.

Fix It is developed by Microsoft and is one of the official troubleshooting tools.

AVG PC Tune Up

The program was created by the developers of the famous AVG antivirus. Downloading and using the program is free. The creators of AVG PC Tune Up promise that computers will work faster after using the utility and will not break down longer.

To use the capabilities of AVG PC Tune Up, just install it and step by step start checking and eliminating errors.

Kaspersky Cleaner

A free utility from a company that offers antivirus software. Kaspersky Cleaner is very easy to use. You can download it.

After launch, the user is asked to press just 1 button to find and fix internal problems of the operating system.

List of system errors for blue screen

Most users begin to worry about the state of the system only when the blue screen of death appears regularly. Below is a list of the most common ones.

The listed errors can be solved by running a scan and fix, rolling back the system, or reinstalling Windows.

Reset settings in BIOS

This method is suitable in cases where the user has installed incorrect settings on the computer, but does not know what exactly the error is. Entering the BIOS on different devices is carried out at the moment of switching on. To launch the BIOS menu, you need to hold down one of the hot keys (you can find out more on the manufacturer’s website). Most often, these are the F8, F10, Del buttons.

On older BIOS types, resetting to default settings was carried out on the main page. “Item Load Fail-Safe Defaults.”

On new PCs and laptops, this function is located in the right “Exit” tab, usually referred to as “Load Setup Defaults”.

Using Safe Mode

In some cases, the system is so damaged that it does not start in the usual window format. You can start checking and eliminating errors in safe mode via the command line (see above).

On most devices, safe mode is launched by frequently pressing the F8 button at startup. A boot menu will appear where you can select an option. The pointer is moved with the up and down buttons, and selection is made with the Enter key.

System Restore

If error correction does not lead to the expected result, you should try to restore the system to a more efficient state. The simplest algorithm:

The computer will restart and function correctly.

Recovery in Windows RE

This method is suitable in cases where nothing helps at all. Recovery in the Windows RE environment is carried out not from the operating system, but from the BIOS. Algorithm of actions:

1. Insert a disk or bootable USB flash drive containing Windows 7;
2. Turn on the device, enter the BIOS;
3. In the Advanced Features section, select starting the PC from a disk or USB device;
4. Reboot;
5. In the menu that opens when loading, select one of the recovery options that suits the user.

It is recommended to select “Startup Repair” to troubleshoot problems and recover damaged files. System Restore performs comprehensive troubleshooting. A command line is also available in Windows RE, through which you can run internal utilities to check and troubleshoot problems.

Report content

• 
  Copyright infringement Spam Incorrect content Broken links
• 
  
• 
  

It is as automated as possible, but errors may occur. Sometimes the cause of this situation is a hardware malfunction, in other cases the BIOS settings or an incorrectly recorded distribution are to blame. In any case, errors when installing Windows 7 can be corrected on your own. This will be helped by an error code that tells the user in which direction to “dig” to fix the problem. So, let's look at the errors that occur most often.

The causes of error 0x80300024 are several factors:

• Incorrect disk partitioning
• There is not enough space to install the system
• Incorrect partition specified for installation.
• Incorrect BIOS settings.

First of all, make sure that the partition you specify during installation contains enough space to store the operating system files. The 32-bit version requires a minimum of 16 GB, the 64-bit version requires 20 GB (excluding other programs, only Windows files). If everything is fine with the volume of the partition, check that it is the main one. If the selected partition is logical and not primary, then it needs to be repartitioned. But first you need to make sure that the problem is in the markup:

1. Press Shift+F10 to launch Command Prompt.
2. Type “discpart” (all commands are entered without quotes) and press Enter.
3. Enter “list disk” to display a list of connected drives on the screen.
4. Display a list of partitions with the “list part” command.

A list of partitions will appear in the command line window. What you're interested in here is the "Type" column. Look at what type of partition you are trying to install the system on. If it is logical, then you need to fix this situation:

1. Create a partition for Windows files using the “create part primary size=N” command. “N” in the command syntax is the size of the allocated space in megabytes. To, for example, allocate 50 GB for the system, write 51200 MB instead of “N”.
2. Format the created partition – format fs=ntfs label=“Windows” (quotes are needed here).
3. Activate the “active” section.
4. Assign a letter to the system partition – “assign letter=C”.

On the remaining free space, you need to create a logical volume for personal information.

1. Type "create partition extended".
2. Type "create partition logical".
3. Format the volume – format fs=ntfs label=“My_Files” (write quotes too).
4. Set the letter – “assign letter=D”.
5. Exit DISKPART with “exit” and close the command prompt.

If you have a UEFI BIOS on your computer, then failure 0x80300024 may be due to the fact that you specified the installation media first in the boot priority. In a regular BIOS, this is done: users go to the “Boot” tab and change the priority so that first either the disk, and then the hard drive.

In UEFI BIOS, the principle is different: you need to go to the “Boot” tab and find the flash drive in the “Change Boot” section. To start from a flash drive, you just need to click on it in the UEFI interface.

Error 0x80070570

Error 0x80070570 appears at the stage of copying system files to the computer's memory. The cause of this failure may be:

• Physical damage to the media (scratches on the disk, broken flash drive, etc.).
• Software corruption of distribution files.
• Faulty RAM.

The error appears when the installation wizard does not access the necessary files due to the latter being unreadable. The installation is interrupted and cannot be resumed until the cause of the failure is eliminated.

Error 0x80070017

If the installation program does not see the disk, a message with error code 0x80070017 appears on the screen. The reasons for the failure may be:

• An inoperative disk drive that cannot read media containing the Windows 7 distribution.
• A damaged CD/DVD disk from which data cannot be read (in this case, error 0x80070570 may appear).
• Incorrectly written distribution.

To rule out the possibility of a bad disk, try installing from a different disk. If error 0x80070017 appears again, it is recommended to write the distribution kit to a flash drive and install the “seven” from a removable drive, without using a disk drive.

If necessary, create a partition or partitions and click “Apply”: at this stage problems may arise - when Windows 7 asks for a driver for further installation or when the system does not see your hard drive to continue the installation. In such cases, we recommend returning to the BIOS and switching the operating mode of the SATA controller from AHCI to IDE yourself!

Windows installation is not possible (GPT standard)

This message appears when you try to install a 32-bit version of the OS on a hard drive with GPT partitioning, on which you can only install Windows 7 x64 or Windows 8.1 x64. However, this does not mean that you need to buy and connect another hard drive - you can simply convert GPT to the MBR standard.

The only drawback of this solution is that the MBR standard can only work with disks whose capacity does not exceed 2.2 TB. If you have more space on your hard drive, the amount beyond the limit will not be recognized, meaning you will not be able to use it. During the conversion, all information from the hard drive will be erased, so if you have important files stored on your hard drive, first transfer them to another medium. The conversion procedure itself can be carried out without leaving the installation wizard:

1. Click "Ok" to close the error message.
2. In the installation location selection window (where you get the crash in question), press Shift+F10 to launch the command line.
3. Enter "discpart".
4. Type "list disk" to display a list of all connected drives.
5. Select the desired disk with the command “select disk 0” (if several hard drives are connected, then instead of 0, put its number - 1,2, etc.).
6. Use the “clean” command to clear the disk.
7. Enter "convert mbr" to start the conversion procedure.
8. Wait for the operation to complete and exit the DISKPART utility with the “exit” command.

After converting GPT to MBR, you need to create partitions from the unpartitioned area on the disk for Windows files and personal information, and then continue with the installation.

A few rules that will help you fix errors that occur during the installation of Windows 7:

• If the installation wizard gives an error when installing Windows 7, try using a different bootable media. Write the distribution kit to a USB flash drive to eliminate the impact of a malfunctioning drive on the Windows 7 installation process.
• If you burn an image to DVD, then use special programs like UltraISO. Do not burn through Nero - this will cause the distribution to be burned incorrectly.
• Set the minimum burning speed, since the maximum does not provide high-quality recording of files.

If you are convinced that the drive is working properly, and the installation media is written according to all the rules and works on other computers, but the error when installing Windows 7 does not disappear, then check the RAM. If several sticks are connected to the motherboard, try disconnecting them one by one or swapping them - sometimes this helps fix the problem.