Tried to upgrade to Win 10, got the Error 0x80004005

So decided to try the Win 10 upgrade from Windows 7, and I received the
Error 0x80004005 message. After that, it reverted me automatically back
to Windows 7 again.

Searching through the Internet, I got the following solution to it:

[Solved] (KB3081424) - Error 0x80004005 in windows 10 update
http://www.computing.net/answers/win...update/74.html

So it seems to be caused by a specific patch, KB3081424, causing it.

The solution to it is listed in this article:

Windows 10 patch KB 3081424 can crash, fail to install | InfoWorld
http://www.infoworld.com/article/296...o-install.html

It mentions going into the registry to fix something.

That's all well and good, but how do I apply the fix to this patch under
Windows 7, so that it takes effect in Windows 10? Does making a registry
change in Windows 7 carry over to Win 10?

Yousuf Khan

Yousuf Khan wrote on 12/18/2015 7:33 AM:
So decided to try the Win 10 upgrade from Windows 7, and I received the Error 0x80004005 message. After that, it
reverted me automatically back to Windows 7 again.

Searching through the Internet, I got the following solution to it:

[Solved] (KB3081424) - Error 0x80004005 in windows 10 update
http://www.computing.net/answers/win...update/74.html

So it seems to be caused by a specific patch, KB3081424, causing it.

The solution to it is listed in this article:

Windows 10 patch KB 3081424 can crash, fail to install | InfoWorld
http://www.infoworld.com/article/296...o-install.html

It mentions going into the registry to fix something.

That's all well and good, but how do I apply the fix to this patch under Windows 7, so that it takes effect in Windows
10? Does making a registry change in Windows 7 carry over to Win 10?

Yousuf Khan
How did you do the upgrade?

I went here https://www.microsoft.com/en-us/soft...load/windows10 and ran the tool and built my bootable USB copy
of win 10. Currently (or 2 weeks ago) they were downloading the newer November update of win10 10586 not the July
10240 build. That in itself might make a diff.
Either way, once I made the usb, I then re-ran the tool and just told it to upgrade (skip the ISO part).

Big Al wrote:
Yousuf Khan wrote on 12/18/2015 7:33 AM:
So decided to try the Win 10 upgrade from Windows 7, and I received
the Error 0x80004005 message. After that, it
reverted me automatically back to Windows 7 again.

Searching through the Internet, I got the following solution to it:

[Solved] (KB3081424) - Error 0x80004005 in windows 10 update
http://www.computing.net/answers/win...update/74.html


So it seems to be caused by a specific patch, KB3081424, causing it.

The solution to it is listed in this article:

Windows 10 patch KB 3081424 can crash, fail to install | InfoWorld
http://www.infoworld.com/article/296...o-install.html


It mentions going into the registry to fix something.

That's all well and good, but how do I apply the fix to this patch
under Windows 7, so that it takes effect in Windows
10? Does making a registry change in Windows 7 carry over to Win 10?

Yousuf Khan
How did you do the upgrade?

I went here https://www.microsoft.com/en-us/soft...load/windows10
and ran the tool and built my bootable USB copy of win 10. Currently
(or 2 weeks ago) they were downloading the newer November update of
win10 10586 not the July 10240 build. That in itself might make a diff.
Either way, once I made the usb, I then re-ran the tool and just told it
to upgrade (skip the ISO part).



I suspect Yousuf's trying a clean install with one of the Upgrade
releases, and that's how he's got into this Catch-22 situation.
The answer is, of course, to follow your advice above, and download a
proper install version. After that he should run the Upgrade.

I have several Upgrades in WinUpdate Hidden, all around 2.8 GB, whereas
the $Windows.~WS in C: is 5.78 GB.

And yes, if anybody's going to complain that the way he's done it should
have worked, and M$ are at fault, I agree.

Ed

On 18/12/2015 9:30 AM, Big Al wrote:
How did you do the upgrade?

I went here https://www.microsoft.com/en-us/soft...load/windows10
and ran the tool and built my bootable USB copy of win 10. Currently
(or 2 weeks ago) they were downloading the newer November update of
win10 10586 not the July 10240 build. That in itself might make a diff.
Either way, once I made the usb, I then re-ran the tool and just told it
to upgrade (skip the ISO part).

Yeah, I initially did it through the Windows Update route, and the
problem occurred there. So I didn't feel like waiting for the Windows
Update to redownload it all over and over again, so I downloaded the
ISO, and ran it through the DVD drive. It occurred through the DVD route
too.

However, it did ask if I wanted to download the latest patches, maybe I
should tell it not to do that?

Yousuf Khan

Yousuf Khan wrote on 12/18/2015 12:37 PM:
On 18/12/2015 9:30 AM, Big Al wrote:
How did you do the upgrade?

I went here https://www.microsoft.com/en-us/soft...load/windows10
and ran the tool and built my bootable USB copy of win 10. Currently
(or 2 weeks ago) they were downloading the newer November update of
win10 10586 not the July 10240 build. That in itself might make a diff.
Either way, once I made the usb, I then re-ran the tool and just told it
to upgrade (skip the ISO part).

Yeah, I initially did it through the Windows Update route, and the problem occurred there. So I didn't feel like waiting
for the Windows Update to redownload it all over and over again, so I downloaded the ISO, and ran it through the DVD
drive. It occurred through the DVD route too.

However, it did ask if I wanted to download the latest patches, maybe I should tell it not to do that?

Yousuf Khan
I did it with patches on 2 machines and no ill effects.

On 18/12/15 12:33, Yousuf Khan wrote:
So decided to try the Win 10 upgrade from Windows 7, and I received
the Error 0x80004005 message. After that, it reverted me automatically
back to Windows 7 again.


It could be because you are so stupid that you are installing it on your
12 years old puter which was barely able to run XP. Now how can you
expetc it to run Windows 10?

Why don't you buy a new machine from DELL. Any low spec machine from
DELL will run Windows 10.

Yousuf Khan wrote:
On 18/12/2015 9:30 AM, Big Al wrote:
How did you do the upgrade?

I went here https://www.microsoft.com/en-us/soft...load/windows10
and ran the tool and built my bootable USB copy of win 10. Currently
(or 2 weeks ago) they were downloading the newer November update of
win10 10586 not the July 10240 build. That in itself might make a diff.
Either way, once I made the usb, I then re-ran the tool and just told it
to upgrade (skip the ISO part).

Yeah, I initially did it through the Windows Update route, and the
problem occurred there. So I didn't feel like waiting for the Windows
Update to redownload it all over and over again, so I downloaded the
ISO, and ran it through the DVD drive. It occurred through the DVD route
too.

However, it did ask if I wanted to download the latest patches, maybe I
should tell it not to do that?

Yousuf Khan

When that happens, you would likely:

1) Examine the setupact.log or CBS.log or whatever.
See why it actually failed. The files in question
might be in C:\$WINDOWS.~BT.

2) Use CheckSUR (Win7SP1) or DISM (Win8.1) to
repair the qualifying OS before next install attempt,
in case the Windows Store on the qualifying OS is causing
a problem.

3) Now, try to install using the DVD.

Version 10586 is equipped to accept the qualifying
OS license key directly. So in theory, with 10586,
you can do a *clean* install of Windows 10 without
going through a Digital Entitlement step, using
the key off the COA on the machine. In the case
of an OEM computer, like a Dell with 8.1 on it,
the DVD should be able to hoover the key out of
the BIOS table all by itself.

You have many options for escape.

And I hope you made a backup before you started...

Paul

On 18/12/2015 12:13 PM, Ed Cryer wrote:
I suspect Yousuf's trying a clean install with one of the Upgrade
releases, and that's how he's got into this Catch-22 situation.

Nope, just a normal upgrade install.

The registry tree branch that they're talking about doesn't even appear
in the Windows 7 registry.

Yousuf Khan

On 18/12/2015 3:29 PM, Paul wrote:
When that happens, you would likely:

1) Examine the setupact.log or CBS.log or whatever.
See why it actually failed. The files in question
might be in C:\$WINDOWS.~BT.

2) Use CheckSUR (Win7SP1) or DISM (Win8.1) to
repair the qualifying OS before next install attempt,
in case the Windows Store on the qualifying OS is causing
a problem.

CheckSUR doesn't exist under Win7, but DISM does.

3) Now, try to install using the DVD.

Version 10586 is equipped to accept the qualifying
OS license key directly. So in theory, with 10586,
you can do a *clean* install of Windows 10 without
going through a Digital Entitlement step, using
the key off the COA on the machine. In the case
of an OEM computer, like a Dell with 8.1 on it,
the DVD should be able to hoover the key out of
the BIOS table all by itself.

It doesn't even get to the stage of installing the license key.

You have many options for escape.

The Windows 10 install escaped all by itself.

And I hope you made a backup before you started...

Yup, but so far haven't needed it, it escaped back to Win 7 without any
modifications.

Yousuf Khan

Yousuf Khan wrote:
On 18/12/2015 3:29 PM, Paul wrote:
When that happens, you would likely:

1) Examine the setupact.log or CBS.log or whatever.
See why it actually failed. The files in question
might be in C:\$WINDOWS.~BT.

2) Use CheckSUR (Win7SP1) or DISM (Win8.1) to
repair the qualifying OS before next install attempt,
in case the Windows Store on the qualifying OS is causing
a problem.

CheckSUR doesn't exist under Win7, but DISM does.

3) Now, try to install using the DVD.

Version 10586 is equipped to accept the qualifying
OS license key directly. So in theory, with 10586,
you can do a *clean* install of Windows 10 without
going through a Digital Entitlement step, using
the key off the COA on the machine. In the case
of an OEM computer, like a Dell with 8.1 on it,
the DVD should be able to hoover the key out of
the BIOS table all by itself.

It doesn't even get to the stage of installing the license key.

You have many options for escape.

The Windows 10 install escaped all by itself.

And I hope you made a backup before you started...

Yup, but so far haven't needed it, it escaped back to Win 7 without any
modifications.

Yousuf Khan


CheckSUR does exist under Windows 7. You *download*
a copy.

The copy of DISM on Windows 7 is not functionally
complete. It does not have the repair functions that
exist in Win8 or Win10. That is why we're forced to
download and use System Update Readiness at the
time of application. You load a fresh copy, as it
can be updated with time.

Try a link in here. As far as I can remember, it
should be several hundred megabytes. I ran it for
fun once.

https://support.microsoft.com/en-us/kb/947821

Paul

On 18/12/2015 19:05, Good Guy wrote:
On 18/12/15 12:33, Yousuf Khan wrote:
So decided to try the Win 10 upgrade from Windows 7, and I received
the Error 0x80004005 message. After that, it reverted me automatically
back to Windows 7 again.


It could be because you are so stupid that you are installing it on your
12 years old puter which was barely able to run XP. Now how can you
expetc it to run Windows 10?

Why don't you buy a new machine from DELL. Any low spec machine from
DELL will run Windows 10.


As an exercise I installed 32bit W10 on an old ACER 2003 Travelmate 4020
laptop just to see if I could. It originally had XP running happily.
Anyway it all seems to be working fine, and in fact has just updated
itself to the latest Insider Preview version 11082.

En el artículo , Yousuf
Khan escribió:

Yup, but so far haven't needed it, it escaped back to Win 7 without any
modifications.

You should consider that you had a narrow escape and stick with 7.
Win10 is a privacy-raping pile of ****.

There's no such thing as a free lunch.

--
(\_/)
(='.'=) Bunny says: Windows 10? Nein danke!
(")_(")

On 19/12/2015 6:08 AM, Mike Tomlinson wrote:
En el artículo , Yousuf
Khan escribió:

Yup, but so far haven't needed it, it escaped back to Win 7 without any
modifications.

You should consider that you had a narrow escape and stick with 7.
Win10 is a privacy-raping pile of ****.

Well, I considered that too, but I want to get setup for DirectX 12
ahead of time, to get ready for it.

Yousuf Khan

On 19/12/2015 4:13 AM, Oldster wrote:
As an exercise I installed 32bit W10 on an old ACER 2003 Travelmate 4020
laptop just to see if I could. It originally had XP running happily.
Anyway it all seems to be working fine, and in fact has just updated
itself to the latest Insider Preview version 11082.

It's best not to answer the troll.

Yousuf Khan