July 13, 2015 at 17:53How I Tamed Windows Update and Received an Invite to Windows 10 Reserve
Today I will tell one story, which, perhaps, will be the quintessence of all the useful material that I have used throughout this thorny path.
In the distant, distant 2014, in the cold-cold (by the way, not so cold) November, my laptop from the Mesozoic year 2010, after a sudden power outage during the installation of updates, grabbed a hard switch. Well, I think it happens, turned it on, and as if nothing had happened continued his work. But the very next day, after a weekly pack of updates for the OS, I noticed a very strange thing: during the scheduled restart after the next KBxxxxxx restart, the system "Cannot complete the updates", which it tells us clearly 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 o’clock in the morning, therefore, it is extremely difficult to register an act of violation of the update procedure, but after a couple of months, as the number of updates accumulates, the volume of the failed software has steadily increased, and, as part of a six-month planned round 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 say the least, is impressive. When trying to install at least one of them, the log threw various errors at me, for example, “I can’t read the update manifest”, or, more complicated, the same one “We were unable to complete the updates. Rollback of changes. " After many days wandering around the Internet, I managed to resolve all the problems associated with updates, and now I’ll tell you what to do,
The first step is 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 thing weighs about ~ 150MB, finds infection, in my case it was 4 keygens, and, if necessary, removes it by order of the user.
After we make sure that our patient is healthy, go to step 2.
If we are tormented by an error with the code 0x80070490, then it's time to display the command line with elevated privileges on the battlefield (cmd.exe on behalf of the Administrator). What follows is described in the article dedicated to solving the problem under the number 80070490: “Windows Update Error 0x80070490” .
After completing the many-hour (and, in my case, almost daily) system scan with subsequent recovery, we move on.
It often happens that an error code does not provide reliable information about solving a problem caused by error 0x80070005. But, fortunately for you, my dear readers, I have successfully dealt with this annoying misunderstanding! The solution to the problem is 0x80070005 .
For those who, for some reason, once long ago deactivated the Super Administrator account (after activating it with the “net user Admin / active: yes” command), there is a solution to the inconvenience associated with the constant and undesirable viewing of the icon of this account on the welcome screen , which consists in hiding selected accounts from the logon screen. If the above command is unfamiliar to you, and there is no icon on the welcome screen with the name Administrator, you can go directly to step 5.
At the command prompt, on behalf of the Administrator, execute the command:
We get a list with the names of all available accounts. We are looking for the Administrator account in this list (in English, respectively, Administrator).
Enter the command:
The seventh line must correspond to Yes, otherwise the account must be activated with the command:
After a successful command, open the Registry Editor (regedit.exe).
In chapter:
you must create a subsection called SpecialAccounts in which to create a subsection named UserList. The result should be the path:
In this section, you need to create a parameter named "Administrator" of type REG_DWORD. The parameter value does not need to be changed, because 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 W7HP on board and on a similar one, but with W8Pro.
Without going into details, in short:
Antiviruses like to monitor changes to the registry, and when registering such an event, they immediately inform the user about the incident, asking permission to make these same changes. During the installation of the whole set following Update 1, I watched this dialog box more than three hundred times.
By going to the registry along the path:
and finding there complete chaos in the permissions of this section, I returned everything back, focusing on the registry of a healthy computer.
The same manipulations must be performed in the section
After brainstorming, after fixing the permissions, it was decided to remove the antivirus (in my case it was ESET Nod32 Antivirus 8), after which the updates that swore at the error from step 3 were successfully installed.
It is possible that, for some reason, the stars in the sky were not located as WX developers wanted, and as a result, not everyone has the opportunity to reserve the Top Ten. Two days of research, megabytes of information read, hundreds of reboots - and the long-awaited Windows logo icon has appeared! To repeat this famous focus of David Copperfield, you need to do just three simple things:
Item number 1:
Check the section:
It should have an UpgEx string parameter with the value “Orange” (I’m not sure about something other than “Orange”, but it worked out for me), if it isn’t, create it.
Thing number 2:
create the root of any disk (in fact, it doesn’t matter where, just the path to the file lying in the root is minimal) the GWX.cmd file (you can also create a file name yourself), into which we put the following script:
Thing number 3:
At the command prompt, execute this script:
Lines 10 should appear in the console window, no more, and the tray should have a new icon with a pop-up text “Get Windows 10”.
The goal is achieved.
Hint list:
- during long-term operations, it is desirable to minimize the load on the hard drive, since checking a million or two 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 best 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, keeping to about the same amount of updates 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 updateability of the operating system on updates 53 and 55. After that, we will start the installation with update 1. Restart. After installing update 1, we will install updates 2 and 3 at the same time, and then restart again. Next, we put updates 4,5,6,7,8,9 and so on, until we type them in ~ 300-400MB, put them in large packs for a very long time, in case of any error they will roll back too long.
- during all kinds of checks like DISM you can make coffee;
- during the check for unwanted and malicious software, you can generally leave the city, return late in the evening and still find the check, it will be approximately 90%, but it will;
- in the process of searching for these solutions, my system was subjected to:
- two reinstallations;
- Six SFC checks;
- Five DISM checks;
- two hundred and seventeen reboots;
- one sudden power outage;
- one mechanical cleaning of dust, including complete disassembly-assembly of the laptop.
Hopefully the above instructions will help someone else besides me.
In the distant, distant 2014, in the cold-cold (by the way, not so cold) November, my laptop from the Mesozoic year 2010, after a sudden power outage during the installation of updates, grabbed a hard switch. Well, I think it happens, turned it on, and as if nothing had happened continued his work. But the very next day, after a weekly pack of updates for the OS, I noticed a very strange thing: during the scheduled restart after the next KBxxxxxx restart, the system "Cannot complete the updates", which it tells us clearly 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 o’clock in the morning, therefore, it is extremely difficult to register an act of violation of the update procedure, but after a couple of months, as the number of updates accumulates, the volume of the failed software has steadily increased, and, as part of a six-month planned round 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 say the least, is impressive. When trying to install at least one of them, the log threw various errors at me, for example, “I can’t read the update manifest”, or, more complicated, the same one “We were unable to complete the updates. Rollback of changes. " After many days wandering around the Internet, I managed to resolve all the problems associated with updates, and now I’ll tell you what to do,
Step 1. Scan for malware and unwanted software
The first step is 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 thing weighs about ~ 150MB, finds infection, in my case it was 4 keygens, and, if necessary, removes it by order of the user.
After we make sure that our patient is healthy, go 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 display the command line with elevated privileges on the battlefield (cmd.exe on behalf of the Administrator). What follows is described in the article dedicated to solving the problem under the number 80070490: “Windows Update Error 0x80070490” .
After completing the many-hour (and, in my case, almost daily) system scan with subsequent recovery, we move on.
Step 3. Access error
It often happens that an error code does not provide reliable information about solving a problem caused by error 0x80070005. But, fortunately for you, my dear readers, I have successfully dealt with this annoying misunderstanding! The solution to the problem is 0x80070005 .
Step 4. Checking the status of the Administrator account (optional)
For those who, for some reason, once long ago deactivated the Super Administrator account (after activating it with the “net user Admin / active: yes” command), there is a solution to the inconvenience associated with the constant and undesirable viewing of the icon of this account on the welcome screen , which consists in hiding selected accounts from the logon screen. If the above command is unfamiliar to you, and there is no icon on the welcome screen with the name Administrator, you can go directly to step 5.
At the command prompt, on behalf of the Administrator, execute the command:
net users
We get a list with the names of all available accounts. We are looking for the Administrator account in this list (in English, respectively, Administrator).
Enter the command:
net user Администратор
The seventh line must correspond to Yes, otherwise the account must be activated with the command:
net user Администратор /active:yes
After a successful command, open the Registry Editor (regedit.exe).
In chapter:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
you must create a subsection called SpecialAccounts in which to create a subsection named UserList. The result should be the path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList
In this section, you need to create a parameter named "Administrator" of type REG_DWORD. The parameter value does not need to be changed, because 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 manifested at all
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 W7HP on board and on a similar one, but with W8Pro.
Without going into details, in short:
Antiviruses like to monitor changes to the registry, and when registering such an event, they immediately inform the user about the incident, asking permission to make these same changes. During the installation of the whole set following Update 1, I watched this dialog box more than three hundred times.
By going to the registry along the path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
and finding there complete chaos in the permissions of this section, I returned everything back, focusing on the registry of a healthy computer.
The same manipulations must be performed in the section
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System
After brainstorming, after fixing the permissions, it was decided to remove the antivirus (in my case it was ESET Nod32 Antivirus 8), after which the updates that swore at the error from step 3 were successfully installed.
Step 6. In the event that 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 as WX developers wanted, and as a result, not everyone has the opportunity to reserve the Top Ten. Two days of research, megabytes of information read, hundreds of reboots - and the long-awaited Windows logo icon has appeared! To repeat this famous focus of David Copperfield, you need to do just three simple things:
Item number 1:
Check the section:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\UpgradeExperienceIndicators
It should have an UpgEx string parameter with the value “Orange” (I’m not sure about something other than “Orange”, but it worked out for me), if it isn’t, create it.
Thing number 2:
create the root of any disk (in fact, it doesn’t matter where, just the path to the file lying in the root is minimal) the GWX.cmd file (you can also create a file name yourself), into which we put 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 prompt, execute this script:
С:/GWX.cmd
Lines 10 should appear in the console window, no more, and the tray should have a new icon with a pop-up text “Get Windows 10”.
The goal is achieved.
Hint list:
- during long-term operations, it is desirable to minimize the load on the hard drive, since checking a million or two 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 best 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, keeping to about the same amount of updates 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 updateability of the operating system on updates 53 and 55. After that, we will start the installation with update 1. Restart. After installing update 1, we will install updates 2 and 3 at the same time, and then restart again. Next, we put updates 4,5,6,7,8,9 and so on, until we type them in ~ 300-400MB, put them in large packs for a very long time, in case of any error they will roll back too long.
- during all kinds of checks like DISM you can make coffee;
- during the check for unwanted and malicious software, you can generally leave the city, return late in the evening and still find the check, it will be approximately 90%, but it will;
- in the process of searching for these solutions, my system was subjected to:
- two reinstallations;
- Six SFC checks;
- Five DISM checks;
- two hundred and seventeen reboots;
- one sudden power outage;
- one mechanical cleaning of dust, including complete disassembly-assembly of the laptop.
Hopefully the above instructions will help someone else besides me.