Why does Windows give an error when reinstalling? Three Reasons to Reinstall Windows Recovery in Windows RE

Found problems with Windows? Today we will tell you how to identify problems operating system and how to start the OS after the update.

from 120 rub. RUB

Taking advantage personal computer over a long period of time, it is impossible to avoid any problems. Sometimes the equipment itself fails, in other cases the reasons incorrect operation associated with the operating system itself.

The most common Windows OS problems (Windows)

  • Activation errors.

In most cases, such a Windows malfunction occurs as a result of updating from the seventh or eighth version to the tenth. An incorrectly performed procedure leads to OS activation failures.

To get rid of a problem with Windows like this, first of all, you should open the start menu, where you select the “Settings” column, then click on the “Update and Security” item, and then proceed to direct activation. Here you need to select the “Go to store” field and see if a valid license is freely available. If it turns out that it is not available, then you need to purchase a new one in the Store.

Also, a similar error occurs if the computer does not have access to the Internet or the firewall settings do not allow the system to complete the activation process via the network.

  • Chrome browser not working correctly.

Problems with Windows caused by any malfunctions in the operation of this Internet browser also in most cases occur with the tenth version of the system. Among such problems, we should highlight slow performance, especially when performing fairly resource-intensive tasks, as well as watching videos. Some users were able to solve this problem by reinstalling Chrome.

  • Folder problem.

Many users note the appearance of such a problem with Windows as incorrect operation mail client. In the new operating system, the program does not allow you to create special subfolders in order to optimally organize mail correspondence.

  • Unstable Wi-Fi operation.

If the problem with Windows that you have encountered is caused by malfunctions wireless network, the simplest action you can try to fix the problem is to restart your PC. But a greater effect can be achieved by disabling the function public access to the wireless network that is active on the system by default. In some cases, turning off this option V Wi-Fi settings, it is possible to increase the stability of such a connection.

  • Windows problems caused by driver problems.

As a rule, this problem is observed on devices with Nvidia video cards, as well as multiple monitors.

To solve it, you need to roll back to previous version drivers.

  • The operating system does not start.

The most common error is Disk Boot Failure, which occurs immediately after turning on the computer. In this case, instead of the usual system boot, a message about this failure appears.

Problems with Windows like this are due to the fact that the operating system cannot recognize the drive from which you tried to start. This can happen for a variety of reasons. For example, a drive was simply inserted into the device, and BIOS settings in turn, such that the disk or flash drive begins to be used to start the system.

Problem when Windows takes a long time to load

If the system does not start for a long time, then it is imperative to disconnect from system unit all third-party devices and only after that you can try to turn on the PC.

Also, among the problems that arise due to the BIOS, it is necessary to highlight it incorrect setting, namely an incorrectly set boot sequence. It is worth emphasizing that such failures can occur at any time, which means that you need to constantly monitor the battery charge on the motherboard to prevent similar problem with system startup.

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 the next program or driver, changes Windows settings, power failure), then it’s easy to get rid of it, just delete the problematic application, or restore the registry or even all the contents 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 there is no way to restore the system " little blood", or completely reinstall it, 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, Trash, History, empty the Program Files\ folder Internet Explorer\ Plugins with IE plugins (to restore them, do backups). 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. Clear 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 Ad-Aware, scan HDD utilities such as ScanDisk, Norton DiskDoctor (with the mandatory inclusion of recording 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 request for search engine(for maximum search efficiency, try formulating your query with several different ways). Find a solution in the database Microsoft data- most quick way troubleshooting. If in Microsoft database there is no information about your failure, 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, then the message “ blue screen death" will not be displayed. Therefore, in the Control Panel - System - Startup and Recovery - Settings menu, 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 dedicated to operating systems, software and computer equipment. 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 the keyboard settings set it to default English language. Also check all settings in the options of the applications you use.
  2. Return to the initial state settings in the registry and in the configuration files user.ini, system.ini made using tweaking utilities. 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 the current security policy settings in the Editor group policies 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. Good description assignment of Windows XP services, which will help you find out the initial and recommended status of their configuration in different versions of Windows, you can find 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 settings in the HKEY_LOCAL_MACHINE\ SOFTWARE registry branch the desired program and click on it right click mice. Select the “Permissions” command from the menu that appears and set full access to this registry hive 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 if you delete your account(and the entire user profile) and then create 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 settings refers to an erroneous entry in the registry, 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 problems XP are eliminated if you restore the main boot entry hard drive (MBR) using the “fdisk /mbr” command after starting the PC from a Windows 98 floppy disk (this is necessary for subsequent rewriting of the disk ID), or 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 user group “System” and “Administrators” must have full access rights to the root directory system disk and to the file virtual memory 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 registry accesses, File Monitor - monitoring of file accesses, DllView - information about libraries used by current processes, OpenList - information about all open files, PortMon - calls to ports, TCPView - information about connections via the TCP protocol. Display information about everyone running programs The TaskInfo program does the best job. It will also show how many resources central processor consumes every application. 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 parameters when working with programs command line(220 characters or more).

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 more powerful block 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 source uninterruptible power supply. Check the quality of the telephone cable, network cable, electrical wiring.
  5. Remove everything additional devices from the PC (except for the hard drive and video card, although sometimes replacing the video card helps), even the internal tweeter speaker, then in crash protection mode, using the “System Properties” dialog, remove their drivers and look - is the glitch 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 is 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 boot Windows menu), or in system properties, roll back to previous version drivers.

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

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 section under Windows files with the command “create part primary size=N”. “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 cannot 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:

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

To exclude 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 space 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 DISKPART utilities with the "exit" command.

After converting GPT to MBR, you need to create partitions from the unallocated 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 another 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 RAM. If to motherboard Several strips are connected, try disconnecting them one by one or swapping them - sometimes this helps fix the problem.

“What does it cost us to build a house”? This is probably what many not-so-prudent users think when thinking about reinstalling the system. They believe that this is an easy and hassle-free task, therefore, with persistence worthy of better use, they step on the same rake over and over again. We assure you, competent installationWindows– the task is quite complex and troublesome, therefore it must be solved either by employees service center, or knowledgeable about IT-technology friends and colleagues. Moreover, even professionals sometimes make gross and unforgivable mistakes, but in order to preserve the “honor of the uniform,” clients are given a different version, in which the role of the main villain goes to (surprise, surprise!) Microsoft. Interested? Let's find out!

  1. Installation from a working system

Theoretically, this is indeed possible, and you will even be able to keep all stopped programs intact. Practice, however, turns out to be not so rosy, especially if the “parent” OS resembles a nuclear weapons testing site. Numerous errors in the registry, traces of viruses, not completely remote programs, conflicting drivers, the ubiquitous Kaspersky antivirus (classic BSOD and klif.sys failure) ... All this disgrace comfortably moves to a new system and continues to bother the user with various problems.

Tip: install the OS only (!) on a pre-formatted hard drive partition!

  1. Installation from a problematic distribution

If your installation disk is licensed, you can safely move on to the next section. But if you “legally” downloaded Windows from one of the many trackers, get ready for surprises, and pitfalls there's more than enough here. This could be a “crooked” activator that replaces critical system files, incorrect system tweaks, missing drivers for major computer components, or security features disabled by default. As a result, you get a “clean” system that refuses to accept half of the usual application software and routinely crashes when you try to install an antivirus.

Advice: use only copies of a licensed disk or verified and reliable assemblies, and you will have to decide on the legality of such actions yourself.

  1. Installing the incorrect OS version

This often affects owners of rather outdated computers from 10–15 years ago, who abruptly remember what is happening in the yard. XXIcentury and it’s time to try something new and modern, and not install it againWindows XP. Arguments that it is pointless to install G8 on such ancient hardware do not work on them, as a result of which the initial download (if by some miracle the installation is completed successfully) lasts 5–10 minutes. However, sometimes the opposite situation happens when newest computer with Intel Haswell or even Broadwell, a gamer nostalgic for old games is trying to “shove” the same XP.

Good old XP is simply no longer suitable for modern PCs

Advice: the version of the system being installed and the available hardware must approximately correspond to each other, and any excesses in this matter are fraught with big problems.

  1. “Forgetfulness” when saving user settings

A very popular mistake among people. A computer owner, preoccupied with thoughts of future dividends in the form of net and fast system, “forgets” that on drive C: he still has a lot of Word documents, part of his home photo archive and several very piquant pictures of the corresponding nature. And although everything system administrators urge users not to store work data on the system partition; usually no one listens to them. As a result, the user receives not only a clean system, but also a headache from the fact that the data will have to be restored somehow.

Advice: before installing the system, first copy all your data to another partition (or better yet, an independent physical disk), and then make a backup copy of the system using Acronis or Paragon. Don't know what it is or how to turn it on? hidden files? Ask a qualified friend or more knowledgeable colleagues for help, and let someone else deal with the inevitable bumps!

  1. Incorrect order of installing drivers and system software

Widespread and very common mistake, which Ilf and Petrov warned about at one time. Remember the catchphrase “money in the morning, chairs in the evening”, uttered by the fitter Mechnikov? So, it is directly related to our topic today. That is, you need to search for and prepare drivers not after installing the OS, but before! It is important to ensure that they are intended for Windows versions, which you intend to install. This, by the way, is the main danger of a “software” upgrade, when the new system refuses to recognize the sound controller or USB 3.0 hub (quite typical for many laptops).

If installed incorrectly, you can forget about 3.0 connectors

Tip: Preparing drivers for all devices is the most important preparatory step when installing Windows. But you shouldn’t count on the features integrated into the distribution, since they are designed only to implement basic functions, and, to put it mildly, do not suffer from an excess of features.

  1. Neglecting to install system software

If you believe that the drive that manufacturers motherboards complete their products, is a panacea for all diseases, then you are deeply mistaken. After all, for proper operation majority modern games and application packages require at least three more components: DirectX, librariesMicrosoft Visual C++ and the client part of the platform.NET Framework. But they don’t always come complete with motherboard or video card. It is also worth taking care of support for modern Internet technologies from Adobe (Flash, AIR and Shockwave).

Required Products

Advice: do not put off installing additional software until later. Nothing good will come of this, and the “saved” time will result in serious problems in the very near future!

  1. Refusal to install antivirus

Basic FeaturesWindows for protection against various Internet garbage are quite modest, and the thesis about the “uselessness” of an antivirus is actually a harmful and very dangerous myth. Moreover, you should not justify your own laziness by the complexity or high price of the corresponding programs. Firstly, the cost of most complex protective solutions is very humane (about 1000 rubles). Secondly, even the available “free” versions of commercial programs (Avast, Avira, AVG) provide a sufficient level of counteraction to modern Internet threats. Thirdly, reputable vendors quite often hold various promotions, during which you can download for free the antivirus that you were asking for money for yesterday.

Advice: do not neglect the protection of your computer in hopes of the traditional Russian “maybe”. And if you don’t believe me, take a stroll through two or three “adult” sites, and then spend several hours emergency ridding your system of yet another Winlock. Alas and ah, but in modern conditions A reliable antivirus is not a whim, but an urgent necessity!

The smooth operation of the PC, as well as the user’s peace of mind about the safety and security of personal information and data, completely depend on how stable and competently the operating system is installed. Therefore, the importance of correct Windows installations difficult to overestimate. In fact, it is better to entrust such complex and painstaking work as reinstalling the OS to specialists. The main difficulties of this event include the occurrence of a number of inconveniences (using a floppy disk with program files, or difficulties when reinstalling the OS on a netbook due to the lack of a disk drive), as well as risky situations with losses vital information. Therefore, an important point is to identify the problem: to save the OS or to reinstall it. Reinstalling the operating system is a last resort measure that is taken if there is no other way to solve the problem. There are often cases when correct Windows work Easily resolvable conflicts in computer hardware cause inconvenience. In this case, reinstallation can be avoided.

Installing windows xp on an ssd allows you to improve the quality and speed of using applications. All new PCs require the installation of an OS; reinstalling the system is necessary in cases where the user prefers one system over another (many people do not like XP or others), or in the event that it is impossible to return the old OS to normal operation.

By itself, a “clean” operating system does not allow you to fully use a PC, since you need to install drivers, various user applications and carry out proper system optimization.

Reasons for reinstallation operating system

The main aspect is understanding the relevance of the process. Often this procedure“assigned” when the body of the system is damaged. Symptoms of damage are disruptions in normal booting Windows or unstable PC operation. In this case, reinstallation is the only chance to restore full functionality of the PC.

The process itself is quite complicated, so immediately realistically calculate your capabilities and before it’s too late, seek help from IT experts. Only those who have special skills and knowledge in this area can perform a competent reinstallation. Lack of experience can affect the quality of the “new” OS, the operation of which will differ little from the previous system.