Dear All,
I am running Windows 10 v 1909 on an amd64 kaveri box.
I am having difficulty upgrading the 2004 update.
I am getting the 0x80070002 error.
I have tried quite a few different approaches to beating it but do far it has refused to install.
Suggestions on the best way to get round this would be appreciated.
Regards
Michael Fothergill
Hi Mike.
Does this description fit your system?
Maybe you could post a disk management screen shot.
Disk Management - How to Post a Screenshot of
Many thanks for your reply. I am using a dual boot set up which has both Debian and Gentoo OSes on the same disk alongside Windows.
I have attached a snip file with the disk management output present in it.
On my disk, Windows lives in a partition of 146 GB.
The 300MB partition is a grub style boot partition. The 97.66GB partition is the gentoo OS root partition and the 341.68GB partition is the Debian OS partition.
The 13.88 GB partition is a swap disk partition that is used by both linux OSes.
Cheers
MF
That shot seems to fit the bill although the second "Active" partition is not labelled as a Window special partition, System Reserved or EFI.
Is this configuration new or I guess a better question, "Have you been able to do Feature updates in the past with all these partitions installed? ".
The second partition I think was an attempt at at UEFI install that I abandoned a little while ago and went back to an ordinary bios install.
It's an abandoned EFI partition.
I have been able to install feature updates in the past to Windows.
I am prone to reinstalling the linux Oses from time to time.
But windows carries on.
Regards
MF
Not so much have you been able to install Feature updates, have you been able to install feature updates with your Grub style boot loader installed.
Many thanks for your response.
The answer is yes. I have been using grub2 for ages now and have not had a problem with updates.
The EFI partition is relatively new. Since I am not using it I could delete it and see if that helps.
Regards
MF
If you are on 1909 I would wait for a few months before going V2004. Let them work out the kinks.
I would blame using upgrade assistant, it's known to move files around instead of updating system in place, better wait for windows update using "check for updates"I am having difficulty upgrading the 2004 update.
Detailed description of the error is bellow:
Code:C:\tools> .\err* 0x80070002 # for hex 0x80070002 / decimal -2147024894 COR_E_FILENOTFOUND corerror.h DIERR_NOTFOUND dinput.h DIERR_OBJECTNOTFOUND dinput.h STIERR_OBJECTNOTFOUND stierr.h DRM_E_WIN32_FILE_NOT_FOUND windowsplayready.h E_FILE_NOT_FOUND wpc.h # as an HRESULT: Severity: FAILURE (1), FACILITY_NTWIN32 (0x7), Code 0x2 # for hex 0x2 / decimal 2 STATUS_WAIT_2 ntstatus.h # as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x2 ERROR_FILE_NOT_FOUND winerror.h # The system cannot find the file specified. # 8 matches found for "0x80070002"
This is to confirm the above:
Code Error Description
0x80070002 ERROR_FILE_NOT_FOUND The system cannot find the file specified.
Run setupdiag > post a share link with all of the files into the thread: (one drive, drop box, or google drive
https://docs.microsoft.com/en-us/win...rade/setupdiag
Quote
