Windows 7 recovery tool cannot repair. Windows OS won't load

Starting around September 2015 (the month may differ depending on the region), Yota included a new method for recognizing unwanted Internet distribution from a mobile device, which consists of analyzing the traffic content.

The essence of the new method

In the case of the old detection method (TTL), the blocking worked almost instantly, since the provider receives TTL data in each data packet transmitted by the device. But he's pretty.

The new method complements the old one and includes blocking based on your activity by analyzing traffic. From time to time, your computer requests system updates, antivirus updates, and accesses the game servers of Steam, Origin, Battle.net, World of Tanks, and the like. All this traffic is not typical for mobile devices, and when it is detected, Iota quite rightly believes that an unauthorized distribution of the Internet is occurring.

I can assume that there is a certain quota for such “suspicious” calls to prevent false positives, after exceeding which you receive an offer to pay for the distribution. Thus, blocking does not occur instantly, but from time to time, which can complicate the diagnosis of the source of blocking.

How to bypass the new blocking method?

To do this, you need not to show “suspicious” traffic to Yota.

There are several options for approach:

1. Block those servers that Yota analyzes through the Hosts file. The method is real, but you will stop receiving updates for the system and programs, and you will also not be able to connect to some games. If you are happy with this, then the current blocking lists can be found, and.
2. Block some servers, let others through proxies. Less radical, but also more complex. You block some of the servers that you don’t need according to the first point (for example, these could be Microsoft servers for updates), and in each program that you need (antivirus, Steam, etc.) you specify in the proxy settings the servers through which it will be go traffic. The most difficult thing in this method is to find a good proxy that will not significantly reduce the speed and will be constantly available. Free proxies can be found on HideMe and HideMyAss. I advise only experienced users to use this method. Proxies are quite unstable and need to be changed frequently. They also usually have low speed and slow ping, so you can’t play games through them.
3. Use a VPN and route all computer traffic through it. The most universal way. To do this, we simply select a VPN server, download its client (or use the installation instructions) and launch it. There are paid and free VPNs. Paid ones are good for speed, the ability to select a country (you can bypass regional blocking), guaranteed availability and the absence of restrictions on ports and types of traffic (at the same time, you can download torrents through Yota). I recommend from paid ones

Windows 7 has become a classic for home use; it is installed on every second computer, despite the development of new operating systems from Microsoft. Having entered the market in 2009, the “seven” still cannot get rid of problems during the launch, which pretty much spoil the nerves of the multi-million user audience. To simplify the life of a user whose computer is running “Seven”, this article was written. In it we will look at how to restore Windows 7 if it does not start.

BOOTMGR is missing

The most common problem that appears during the launch of the “seven”.

The reasons for its appearance may be:

• damaged hard drive sectors or non-working SSD memory cells on which Windows 7 is installed (in most cases, you can restore them);
• spontaneous power outage or reboot of the PC using the “Reset” key;
• virus activity (very rare);
• incompetent user handling of hard disk partitioning utilities.

There are several ways to make the error disappear. We will look at how to restore a computer using the OS itself.

• If you encounter problems while starting Windows 7, press F8 to bring up a menu with a list of additional computer startup options.
• Select the “Troubleshooting…” option.

• Select Russian language and click “Next”.
• Select an account with administrator rights.
• Click on “Startup Repair” so that the operating system tries to find and fix the problem on its own.

• If the error is not corrected, launch the command line from the OS renewal options window.
• We enter the commands sequentially:

“bootrec.exe /FixMbr” – writes MBR to the system partition;

“bootrec.exe /FixBoot” - creates a boot record on the system volume.

• Reboot and start the computer.

If after following the steps above, the PC still does not detect Windows 7 installed during startup, run the bootrec.exe command with the “RebuildBcd” attribute through the command line.

It will scan all long-term storage devices installed on your computer for the presence of operating systems installed on them that are compatible with the “seven”, and will allow you to add them to the download list.

And in the very last case, when nothing helps to restore the launch of the “seven”, reserve the old BCD folder, which is responsible for starting the PC, and create a new one. This is done using the following chain of commands:

"Disk boot failure" problem or message with the text "Insert system disk"

The startup error is caused by one of several reasons, the essence of which is the following: the computer is trying to find a boot entry on a disk that is not bootable. Factors that prevent Windows 7 from starting:

• The device from which the computer starts to boot is not the system drive - try disconnecting all flash drives, phone, camera, including external hard drives, and rebooting the system.
• Check the BIOS settings that determine the priority of boot devices - there is a high probability that the computer starts booting from a disk that is not the system one. Also look in the BIOS or through one of the special utilities on which Windows 7 is installed.
• Reconnect the HDD to a different cable and power cable; perhaps the problem lies in the unreliability of the connection or damage to one of the cables, for example, due to its significant bend.

The list of reasons can easily include the absence of Windows 7 installed due to the fact that the disk with it was formatted due to the carelessness or inexperience of a novice user, and reinstalling it or restoring a deleted partition will help here.

If none of the options brings the desired result, try restoring the OS as described in the previous paragraph, and also make sure that the hard drive is working.

Inability to start Windows due to damaged registry files

Among other things, Windows 7 may not boot due to damaged registry files.

As a result, the computer will inform the user about the problem and launch an application that allows you to restore the operating system.

But the Windows 7 automatic recovery tool is not always effective and, for example, if there is no backup copy of damaged data, the user will have to manually restore the operating system.

• Call up a window with an extended list of Windows launch options using F8.
• Select “Troubleshooting...”.
• Next, click on the link: “System Restore.”

Before you figure out how to restore Windows 7 to start, you need to understand what the cause of the problem is. To do this, it will be useful to learn a little general information about how the download occurs and what stages it includes.

General information about downloading

Conventionally, the launch of Windows 7 can be divided into three stages, which, in turn, are divided into several phases.

OSLoader

This is the first stage of system startup, which starts immediately after the BIOS code is executed. First, a small group of drivers starts working, allowing you to read data from the hard drive. The Windows 7 boot loader (winload.exe) then begins initializing and loading the kernel. The registry hive “SYSTEM” and another group of drivers are loaded into RAM. The first stage lasts about 2 seconds and ends with the appearance of the operating system logo on the screen.

MailPathBoot

The main and longest stage of system startup. Visually, it continues from the appearance of the logo until the desktop starts loading. It consists of several phases, the duration of which can vary - from a few seconds to a couple of minutes.

PreSMSS

During this phase, the Windows kernel is initialized, the plug and play device manager starts working, and the remaining drivers are launched. Errors that occur at this moment are usually associated with problems with the main components of the computer or incorrect operation of their software.

SMSSInit

The visual start of this phase is difficult to determine, but part of it is already the empty field that appears between the splash screen and the appearance of the welcome screen. The system at this moment performs the following actions:

• Initializes the registry.
• Starts the next wave of drivers that are not marked "BOOT_START".
• Starts subsystem processes.

Most often, problems during this boot phase are related to video card drivers.

WinLogonInit

WInlogon.exe is the file that launches the welcome screen, so the “WinLogonInit” phase begins at this point. During this stage, group policy scripts are executed and services are started. The duration of the phase varies greatly depending on the processor power.

Failures at this stage are often caused by incorrect operation of third-party applications, including antivirus.

ExplorerInit

Begins with the start of the shell and ends with the start of the window manager. During this phase, program icons appear on the desktop and services continue to start. These processes are accompanied by an increase in the load on the computer hardware - processor, RAM, hard drive.

Problems at this stage are usually associated with insufficient power of the equipment or its malfunction.

PastBoot

The last stage, which begins with the appearance of the desktop and ends after all startup components have loaded. At this stage, all applications that start with Windows begin to work. After the “PastBoot” stage ends, the system goes into idle mode.

Problems that arise at this stage are usually related to virus activity or incorrect operation of automatically downloaded programs.

Crashes at various stages of loading

Problems at different stages of Windows startup manifest themselves differently: some are related to hardware, others to the registry, and others to drivers or important system files. Therefore, it is so important to understand what processes occur when the system starts up so that you can quickly determine the cause of the problem.

Hardware problems

It is often difficult to determine what is not working - some specific hardware or operating system. However, based on some signs, certain assumptions can be made about which device has failed:

All the errors described are usually related to the computer hardware, however, there may be exceptions.

Boot files are damaged

The appearance of a message like “Bootmgr is missing” at an early stage of system startup indicates the absence of critical files, without which Windows cannot boot.
However, sometimes no notifications appear - the cursor just blinks on the screen, but no progress occurs.

Bootmgr is a standard Windows boot loader that is not accessible to the user, as it is stored on a separate hidden partition. You cannot accidentally delete it, but you can unknowingly format a hidden volume using external media.

When booting from external media, the hidden volume with the bootloader looks like this:

Other files important for startup are stored on the system disk in the “Windows” directory. System registry data is also stored here.

The registry is damaged

If the registry is damaged or inaccessible, Windows may not even start loading. In this case, the system usually diagnoses the error on its own and offers to run the recovery tool.

Often, the built-in system restore tool can help you fix a registry problem by copying its configuration files from a backup store. However, there are situations when there are no registry files on the hard drive or they are inoperative. In this case, the user must manually perform the system registry recovery procedure.

Startup recovery tools

The easiest way to restore startup is to use the built-in Windows tools:

A list of means for restoring system functionality will appear, in which you must select “Startup recovery”.
It will scan and automatically correct any errors found, if possible.

If nothing worked with the startup, you can try to restore the system by rolling it back to its previous state. Everything is standard here: select a control point with a working configuration and return the system to that period.

Another method that often helps is restoring the Windows bootloader via the command line. You can also launch it through the “Recovery Options” menu. On the command line you need to enter several queries (all commands are entered without quotes):

After all commands have been successfully completed and the report appears, Windows 7 should start up normally.

One of the worst troubles that can happen to your computer or laptop with windows 7 windows 8 windows 8.1 or windows 10 installed is boot failure. Then you definitely need to run the startup recovery tool.

It’s good if you have a saved restore point, then you can often start your computer or laptop in safe mode and roll back.

But if Windows 7 does not start, then startup recovery can most often be done in this way; moreover, Windows 7 starts startup recovery on its own.

This option will not work with Windows 10. In it, restore points and even safe mode are disabled by default, and no one turns them on on their own or even suspects it.

Very often, restoring startup when loading Windows 7 can take a very long time, one might say constantly ad infinitum and there will be no result. If the work is urgent, then panic and hassle are all around for a long time.

What to do if the automatic tool does not solve the startup error problem, and the endless recovery is only annoying. Maybe BIOS will help? Maybe if there is no flash drive? The answer to these questions is below

How to restore startup if Windows 7 crashes

So, you turn on your computer or laptop with Windows 7, but it doesn’t boot. Usually after this the automatic startup recovery starts and spins ad infinitum.

This happens because the system looks for a restore point, but does not find it and keeps trying again. Turn off. None of this will work if it doesn't work out the first time.

To fix the problem, you need an installation disk, which of course you don’t have. If it is not night, and you have high-speed Internet, then the situation can be corrected.

Download Windows 7 OS from the Internet, but be sure to have the same bit depth as the one you have installed. Damn there's a nuisance I didn't think about. How to download if your computer or laptop won’t start.

Yes, if there is only one PC and there is no way to download it, you need to go to your friends, otherwise there is no other way. Let's assume it's downloaded. Next, you will need a disk or flash drive to burn the downloaded Windows 7.

I won’t describe how to record hundreds of instructions online, including videos. If everything is ready, change the BIOS settings to boot from a flash drive or disk and proceed with the installation.

During installation, we reach the point where you see system recovery. Picture below.

Click on it. The system will search and find your OS

Now, as you can see in the figure below, select startup recovery and wait for the system to restore it.

This is the best way out of such a critical situation. What to do if there is no disk with the OS.

Another startup recovery option

If there is no disk with the recorded OS, but perhaps you have a friend who has a computer or laptop running Windows 7 of the same bitness as you.

Then go to him, buy a blank DVD on the way, and come back and use a friend’s PC to make a recovery disk.

I won’t describe how either, otherwise it will be a book. You'll find it on the web. After this, when you come home, you can restore your PC to start.

Startup recovery on Windows 10

On Windows 10, the option described above will also work, but don’t rush. Although Safe Mode is disabled by default, you can still enable it.

To do this, you will need to emergency shut down your laptop or computer three times in a row.

As soon as you see the logo, immediately force it to turn off, you can even turn off the power if it doesn’t work with the buttons.

The fourth time, you should see a screen with different boot options. Only here again there is a problem.

In version 10, automatic creation of recovery points is disabled, and of course you did not enable it yourself.

Then you have only one option left. Start your PC in safe mode and try to fix errors manually.

Remember what you installed last and remove it. You can also use error correction programs. In short, fix problems.

There is another option. This is the use of a Life SD disk. In this case, you will have the opportunity to edit the registry, and this can only be done by users who understand what they are doing.

It’s easy to find descriptions of how to do this online. I won’t touch on them here; I’ve already almost written a brochure. Good luck.

22.11.2018

The computer does not turn on and says startup recovery. Startup Repair tool not working

The article describes a method by which you can fix the boot disk error that answers that.

Hello. I think there are quite a few of those who have at least once encountered the problem of starting Windows and tried to fix it using a boot disk or the system itself:

I came across a repeated message that the startup repair tool is powerless. Almost no resource I know has offered any clear solution to this problem. And, except for sending the user to reinstall Windows, they do not advise anything.

I offer you a solution to the problem by correcting some Windows registry entries that cause the recovery tool to fail in a circular manner. In general, the principle is simple - we will substitute files from the registry backup into the non-working copy of Windows. In fact, we will do what Windows itself is trying to do - only we will do it manually and for sure. Works on any version of Windows. Or it doesn't work...

Some recently installed programs will have to be sacrificed.

BEFORE YOU START.

• I hope that all the funds have already been used by you; For some people, downloading helps a lot Latest configuration with working parameters
• try to follow the advice carefully, otherwise, after rash actions, other means will turn out to be completely useless - the system will be truly broken irrevocably
• I don't give any guarantees, but it's worth checking

On board:

Drive_letter:

My system drive turned out to be D

• Let's check its contents. The fastest way to do this is to issue the command:

dir

if folders appeared like Program Files, Desktop and others, you are in the right place.

• go to the Windows system directory:

cd\windows\system32\config

where we will again display its contents for better navigation with the dir command and create a folder that will contain the files with which we will work (in case something goes wrong). I named the new folder backup - the name is arbitrary:

• and copy all the contents of the directory into this folder:

copy *.* backup

If the first attempt does not work and you have to rewrite the content, press A in response to the console question.

ATTENTION. At this stage, you should not experience any errors. If something goes wrong, repeat the work from the beginning step by step.

• We are now interested in the contents of the RegBack folder:

cd RegBack

Its content is the same for almost all users and looks something like this (dir command to help):

The main thing is that there are no empty folders with 0 bytes of content.

• Copy the contents of the RegBack folder with the command (follow the syntax):

copy *.* ..

and click on Enter will copy the contents to the directory where the folder is being viewed from (Windows\System32\config). If the console asks for confirmation, press Y or A.

• Close the console and reboot.

Critical errors when starting Windows 7 occur for a variety of reasons: due to hardware failure, due to problems with the system itself, or due to software failures. In some cases, a direct relationship between cause and effect can be traced if a failure occurred after installing an application, driver, connecting a new device, etc. In other cases, the source of the error is difficult to determine.

Hardware problems

Problems that arise before Windows 7 starts loading are related to the hardware, so just a few words about them. The culprit of the failure could be any of the devices, but most often they are RAM and hard drive. The message that appears on the screen in case of a critical error will help you understand in more detail.

Every user has ever seen (BSOD). We will leave most of what is written there behind the scenes, since to make a diagnosis, only the following is important to us:

• error type - a line at the top of the screen, written in capital letters separated by an underscore (item 1 in the picture);
• error code - a numeric identifier in hexadecimal form and its additional parameters (point 2 in the picture);
• the driver or application that caused the BSOD, as well as the address where the failure occurred (point 3 in the picture). In case of problems with the equipment that arise before the initialization of drivers and in a number of other cases, this parameter is not available.

The following data may indicate problems with the hard drive or its controller:

• 0x00000077 - KERNEL_STACK_INPAGE_ERROR
• 0x0000007A - KERNEL_DATA_INPAGE_ERROR
• 0x0000007B - INACCESSIBLE_BOOT_DEVICE
• 0x00000024 - NTFS_FILE_SYSTEM
• 0x0000008E - KERNEL_MODE_EXCEPTION_NOT_HANDLED

Memory errors often make themselves known with messages like this:

• 0x0000002E - DATA_BUS_ERROR
• 0x00000050 - PAGE_FAULT_IN_NONPAGED_AREA
• 0x00000077 - KERNEL_STACK_INPAGE_ERROR
• 0x0000007A - KERNEL_DATA_INPAGE_ERROR
• 0x0000012B - FAULTY_HARDWARE_CORRUPTED_PAGE
• 0x0000007F - UNEXPECTED_KERNEL_MODE_TRAP
• 0x0000004E - PFN_LIST_CORRUPT etc.

Often, RAM malfunction is manifested by a variety of errors that can happen at any time when starting up and operating the computer.

Restoring the BIOS Setup to default settings or, as they say, resetting to default often helps to resolve a simple hardware failure. This can be done in several ways: using your own BIOS option, by switching a special jumper to the mat. board or temporary loss of power to the CMOS chip (BIOS storage location).

Troubleshooting Windows startup problems

Recovery Environment

It is much more convenient to restart Windows 7 than Windows XP, which did not have time to receive the recovery environment. When installing Windows, this environment is installed on the hard drive, has a separate partition, and a separate bootloader. This is why the recovery environment is not affected by the problems that Windows faces.

To launch the recovery environment, press F8 and select "Troubleshoot your computer" from all the Windows boot options.

Next, to get into the recovery environment, the system will ask you to enter a password. If you have forgotten your password or do not have administrator rights, you will have to launch the recovery environment from the installation disk.

You should resort to this point if you do not know the exact reason why Windows does not start.

Select Startup Repair. The system will scan and fix the problems found.

This method can be used if Windows stops loading after installing a program, infecting the computer with viruses, or making changes to the registry.

The System Restore option will help resolve the problem, but only if the restore points have been saved.

The principle of operation is quite simple: you select the desired restore point, which dates back to the time when there were no problems with Windows. The system rollback will begin, after which Windows will boot normally.

Used when there are no backups saved on the computer, but you have a restore point saved on removable media.

Select “System image recovery”, and then connect to the computer a removable drive that contains a system image archive. Next, follow the instructions of the Recovery Wizard.

Manual registry repair

Used when the above instructions did not resolve the problem. On Windows, the registry is backed up every 10 days, so you can try downloading the latest working backup yourself.

• From the list of available options, select Command Prompt and type the following command "notepad" into it, then press Enter. The standard Notepad program will launch. Select the “File” – “Open” menu in the program header.
• Go to directory C:\Windows\System32\config
• At the bottom of the window, in the “File Type” column, change the option to “All Files” to see the full contents of this folder. The following list of files refers to the current registry: Default, Sam, System, Security, Software (no extension).
• Each of these files must be renamed or the extension .old added to them.
• In folder "Config" open the folder "RegBack". This contains registry backups. Copy them one by one to a folder "Config".
• Go back to the window "Recovery Options" and at the very bottom select the button. If the problem is due to a problem in the registry, then Windows will start normally.

Recovery files

Windows has a wonderful built-in utility that perfectly restores protected Windows files. On the menu "Recovery Options" select item "Command line" and write the following command in it:

/scannow /offbootdir=C:\ /offwindir=C:\Windows

Team "scannow" will start a system scan, "offbootdir" indicates the system drive letter, "offwindir" leads to the "Windows" folder.

Please note that the drive letters in the recovery environment may not match those seen when booting Windows normally. Therefore, before you start scanning, be sure to launch Notepad (this process is described above) and check the system drive letter in Explorer.

Manual file recovery

If the methods described above do not bring the desired result, you should try to manually restore boot files, as well as overwrite the master boot record of the HDD.