How I tamed Windows Update and got an invite to reserve Windows 10
Today I will tell one story, which, perhaps, will be the quintessence of all the useful material that I used throughout this thorny path.
Back in the distant 2014 year, in the cold-cold (by the way, not so cold) November, my laptop of the 2010 Mesozoic year of release after a sudden power outage during the installation of updates grabbed hard-switch. Well, I think it happens, I turned it on, and as if nothing had happened, I continued the work. But the next day, after the weekly update pack for the OS, I noticed a very strange thing: when the next “KBxxxxxx” system was restarted after the “Cannot complete updates” system, it clearly tells us before the appearance of the logon screen.
At first, I did not pay attention to it, because the scheduler usually updates the axis at 3 am, therefore, registering an act of violating the update procedure is extremely difficult, but after a couple of months, as updates accumulate, the volume of unsuccessfully installed software grew steadily, and, as part of a six-month planned crawl of system settings, I went to the Update Center Windows, and I saw a terrible figure there - as many as 3 Gigabytes of new updates. The spectacle, to put it mildly, is impressive. When I tried to install at least one of them, the log was thrown at me by various errors, for example, “Unable to read the update manifest”, or, more difficult, that “We failed to complete the updates. Roll back changes. After spending many days wandering across the Internet, I managed to solve all the problems associated with updates, and now I will tell you what to do when nothing is unclear, nothing works, I don’t have the strength to pick it up, but I want to update.
First of all, you need to make sure that we are trying to update a healthy computer. To do this, there is a utility called "Microsoft Safety Scanner" , which can be downloaded from their official website.
')
This piece weighs about ~ 150MB, finds an infection, in my case it was 4 keygens, and, if necessary, removes it by order of the user.
After we have verified that our patient is healthy, proceed to step 2.
If we are tormented by an error with the code 0x80070490, then it's time to bring the command line with elevated privileges on the battlefield (cmd.exe on behalf of the Administrator). What follows what is described in the article devoted to the solution of the problem numbered 80070490: "Error in Windows Update 0x80070490" .
Having completed the many hours (and, in my case, almost daily) scanning of the system with subsequent recovery, we go further.
It often happens that the error code does not give reliable information about the solution of the problem caused by the error 0x80070005. But, fortunately for you, my dear readers, I successfully coped with this annoying misunderstanding! The solution to the problem is 0x80070005 .
For those who, for whatever reason, once deactivated the Super Administrator account (after its activation with the command “net user Administrator / active: yes”), there is a solution to the inconvenience associated with the permanent and unwanted viewing of the account icon on the welcome screen which is to hide selected accounts from logon-screen. If the above command is unfamiliar to you, and there are no icons with the name Administrator on the welcome screen, you can skip to step 5.
On the command line on behalf of the Administrator, execute the command:
Get a list with the names of all existing accounts. We are looking for an Administrator account in this list (in English, respectively, Administrator).
Enter the command:
The seventh line must correspond to the value Yes, otherwise the account must be activated with the command:
After successfully completing the command, open Registry Editor (regedit.exe).
In section:
You need to create a subkey with the name SpecialAccounts, in which you create a subkey with the name UserList. The result should be a way:
In this section, you need to create a parameter with the name "Administrator" of type REG_DWORD. The parameter value does not need to be changed, since 0 - hide the entry, 1 - show. After the reboot, the hidden account will not be displayed in the list of accounts on the user selection screen.
Of the six machines running Windows of different versions (7, 8, 8.1), this problem was identified only on two of them: on a laptop with a W7HP on board and on a similar one, but with a W8Pro.
Without going into details, in brief:
Antiviruses like to keep track of changes to the registry, and when registering such an event, they immediately notify the user about the incident, asking for permission to make these changes. During the installation of the entire set following Update 1, I have watched this dialog box more than three hundred times.
Going to the registry on the way:
and finding there is utter chaos in the permissions of this section, I turned everything back, focusing on the registry of a healthy computer.
The same manipulations must be made in the section.
Having brained, after fixing the permissions, it was decided to remove the antivirus (in my case it was ESET Nod32 Antivirus 8), after which updates that cursed the error from step 3 were successfully installed.
It is possible that for some reason the stars in the sky were not located in the way that the WX developers wanted, and as a result, not everyone has the opportunity to reserve the “Ten” for themselves. Two days of research, megabytes of read information, hundreds of reboots - and the long-awaited icon with the Windows logo has appeared! To repeat this famous trick of David Copperfield, you need to do just three simple things:
Thing number 1:
Check section:
It should have a string parameter UpgEx with the value “Orange” (at the expense of something other than “Orange” - not sure, but with me everything worked out), if not, create it.
Thing number 2:
create in the root of any disk (in fact, no matter where, just the path to the file that is in the root, is minimal) the GWX.cmd file (the file name can also be thought up on its own) in which we place the following script:
Thing number 3:
At the command line, execute this script:
In the console window should appear lines 10, not more, and the tray should get a new icon with a pop-up text "Get Windows 10".
The goal is achieved.
Hint list:
- during long operations, it is desirable to minimize the load on the hard drive, since checking a million or other files is not a trivial task, and it requires full access to the drives;
- Install updates in bulk - the idea is not the best. The most optimal option is to achieve an error-free installation of one or two updates of several kilobytes, and then install updates, starting with the most difficult ones, adhering to approximately the same update volume per iteration. Example:
Update1 (500MB)
Update2 (200MB)
Update3 (150MB)
Update4 (100MB)
Update5 (40MB)
Update6 (35MB)
...
Update53 (24KB)
Update55 (15KB)
First of all, we will test the update of the operating system on updates 53 and 55. After that, we will start the installation with update 1. We will reboot. Installing update 1, install updates 2 and 3 at the same time, and then restart again. Next, we put the updates 4,5,6,7,8,9 and so on, until we get them to ~ 300-400MB, put them in big batches for a very long time, in case of any error they will be rolled back for a long time.
- during any checks like DISM you can brew coffee;
- during the check for unwanted and malicious software, you can leave the city altogether, return late in the evening and still catch the check, it will be about 90%, but it will be;
- in the process of finding these solutions, my system has undergone:
- two reinstallations;
- six SFC checks;
- Five DISM checks;
- two hundred and seventeen reboots;
- one sudden power failure;
- one mechanical dust cleaning, including complete disassembly-assembly of the laptop.
I hope the above instructions will help someone else besides me.
Back in the distant 2014 year, in the cold-cold (by the way, not so cold) November, my laptop of the 2010 Mesozoic year of release after a sudden power outage during the installation of updates grabbed hard-switch. Well, I think it happens, I turned it on, and as if nothing had happened, I continued the work. But the next day, after the weekly update pack for the OS, I noticed a very strange thing: when the next “KBxxxxxx” system was restarted after the “Cannot complete updates” system, it clearly tells us before the appearance of the logon screen.
At first, I did not pay attention to it, because the scheduler usually updates the axis at 3 am, therefore, registering an act of violating the update procedure is extremely difficult, but after a couple of months, as updates accumulate, the volume of unsuccessfully installed software grew steadily, and, as part of a six-month planned crawl of system settings, I went to the Update Center Windows, and I saw a terrible figure there - as many as 3 Gigabytes of new updates. The spectacle, to put it mildly, is impressive. When I tried to install at least one of them, the log was thrown at me by various errors, for example, “Unable to read the update manifest”, or, more difficult, that “We failed to complete the updates. Roll back changes. After spending many days wandering across the Internet, I managed to solve all the problems associated with updates, and now I will tell you what to do when nothing is unclear, nothing works, I don’t have the strength to pick it up, but I want to update.
Step 1. Check for malware and unwanted software.
First of all, you need to make sure that we are trying to update a healthy computer. To do this, there is a utility called "Microsoft Safety Scanner" , which can be downloaded from their official website.
')
This piece weighs about ~ 150MB, finds an infection, in my case it was 4 keygens, and, if necessary, removes it by order of the user.
After we have verified that our patient is healthy, proceed to step 2.
Step 2. Restoring the integrity of system files using the DISM system
If we are tormented by an error with the code 0x80070490, then it's time to bring the command line with elevated privileges on the battlefield (cmd.exe on behalf of the Administrator). What follows what is described in the article devoted to the solution of the problem numbered 80070490: "Error in Windows Update 0x80070490" .
Having completed the many hours (and, in my case, almost daily) scanning of the system with subsequent recovery, we go further.
Step 3. Access error
It often happens that the error code does not give reliable information about the solution of the problem caused by the error 0x80070005. But, fortunately for you, my dear readers, I successfully coped with this annoying misunderstanding! The solution to the problem is 0x80070005 .
Step 4. Check the status of the Administrator account (optional)
For those who, for whatever reason, once deactivated the Super Administrator account (after its activation with the command “net user Administrator / active: yes”), there is a solution to the inconvenience associated with the permanent and unwanted viewing of the account icon on the welcome screen which is to hide selected accounts from logon-screen. If the above command is unfamiliar to you, and there are no icons with the name Administrator on the welcome screen, you can skip to step 5.
On the command line on behalf of the Administrator, execute the command:
net users Get a list with the names of all existing accounts. We are looking for an Administrator account in this list (in English, respectively, Administrator).
Enter the command:
net user The seventh line must correspond to the value Yes, otherwise the account must be activated with the command:
net user /active:yes After successfully completing the command, open Registry Editor (regedit.exe).
In section:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon You need to create a subkey with the name SpecialAccounts, in which you create a subkey with the name UserList. The result should be a way:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList In this section, you need to create a parameter with the name "Administrator" of type REG_DWORD. The parameter value does not need to be changed, since 0 - hide the entry, 1 - show. After the reboot, the hidden account will not be displayed in the list of accounts on the user selection screen.
Step 5. Not all manifest.
Of the six machines running Windows of different versions (7, 8, 8.1), this problem was identified only on two of them: on a laptop with a W7HP on board and on a similar one, but with a W8Pro.
Without going into details, in brief:
Antiviruses like to keep track of changes to the registry, and when registering such an event, they immediately notify the user about the incident, asking for permission to make these changes. During the installation of the entire set following Update 1, I have watched this dialog box more than three hundred times.
Going to the registry on the way:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application and finding there is utter chaos in the permissions of this section, I turned everything back, focusing on the registry of a healthy computer.
The same manipulations must be made in the section.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System Having brained, after fixing the permissions, it was decided to remove the antivirus (in my case it was ESET Nod32 Antivirus 8), after which updates that cursed the error from step 3 were successfully installed.
Step 6. In case the GetWindows10 icon does not appear in the tray after installing the KB3035583 update
It is possible that for some reason the stars in the sky were not located in the way that the WX developers wanted, and as a result, not everyone has the opportunity to reserve the “Ten” for themselves. Two days of research, megabytes of read information, hundreds of reboots - and the long-awaited icon with the Windows logo has appeared! To repeat this famous trick of David Copperfield, you need to do just three simple things:
Thing number 1:
Check section:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\UpgradeExperienceIndicators It should have a string parameter UpgEx with the value “Orange” (at the expense of something other than “Orange” - not sure, but with me everything worked out), if not, create it.
Thing number 2:
create in the root of any disk (in fact, no matter where, just the path to the file that is in the root, is minimal) the GWX.cmd file (the file name can also be thought up on its own) in which we place the following script:
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\UpgradeExperienceIndicators" /v UpgEx | findstr UpgEx if "%errorlevel%" == "0" GOTO RunGWX reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser" /v UtcOnetimeSend /t REG_DWORD /d 1 /f schtasks /run /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" :CompatCheckRunning schtasks /query /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" schtasks /query /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" | findstr Ready if NOT "%errorlevel%" == "1" ping localhost >nul &goto :CompatCheckRunning :RunGWX schtasks /run /TN "\Microsoft\Windows\Setup\gwx\refreshgwxconfig" Thing number 3:
At the command line, execute this script:
:/GWX.cmd In the console window should appear lines 10, not more, and the tray should get a new icon with a pop-up text "Get Windows 10".
The goal is achieved.
Hint list:
- during long operations, it is desirable to minimize the load on the hard drive, since checking a million or other files is not a trivial task, and it requires full access to the drives;
- Install updates in bulk - the idea is not the best. The most optimal option is to achieve an error-free installation of one or two updates of several kilobytes, and then install updates, starting with the most difficult ones, adhering to approximately the same update volume per iteration. Example:
Update1 (500MB)
Update2 (200MB)
Update3 (150MB)
Update4 (100MB)
Update5 (40MB)
Update6 (35MB)
...
Update53 (24KB)
Update55 (15KB)
First of all, we will test the update of the operating system on updates 53 and 55. After that, we will start the installation with update 1. We will reboot. Installing update 1, install updates 2 and 3 at the same time, and then restart again. Next, we put the updates 4,5,6,7,8,9 and so on, until we get them to ~ 300-400MB, put them in big batches for a very long time, in case of any error they will be rolled back for a long time.
- during any checks like DISM you can brew coffee;
- during the check for unwanted and malicious software, you can leave the city altogether, return late in the evening and still catch the check, it will be about 90%, but it will be;
- in the process of finding these solutions, my system has undergone:
- two reinstallations;
- six SFC checks;
- Five DISM checks;
- two hundred and seventeen reboots;
- one sudden power failure;
- one mechanical dust cleaning, including complete disassembly-assembly of the laptop.
I hope the above instructions will help someone else besides me.
Source: https://habr.com/ru/post/355610/
All Articles