I can´t install anything nor update with xbox and the Microsoft Store because I get this error: (0x80070002)

I think you did things correctly, but some ETL files didn't convert correctly.

The WindowsUpdate.log shows entries from 2023/06/09 17:30 to 2023/06/09 17:34, whereas the ProcMon log entries start from 2023/06/09 16:29 PM and end at 2023/06/09 16:31 PM.

That probably means the WindowsUpdate.20230609.162719*.ETL didn't convert correctly. If possible, upload those ETLs if they're still available.

To verify that, I ran a trace on my computer, the ProcMon timestamp and WU log timestamps match exactly. So, some of your ETL files didn't convert.

(The CBS logs look fine. This is not a CBS issue, only a WU/Appx settings issue.)

Try:

• Open Settings → System → Storage → Advanced Storage settings → Where new content is saved.
• Change the "New apps will save to:" and choose a secondary drive letter -- e.g., *D:*

• Open Store and install a new app.

Do you still get the error 80070002?

If so, can you check if this error occurs in other user profile(s)? Please create a new local account to test.

When I went to Settings → System → Storage → Advanced Storage settings → Where new content is saved, I got this, and I don't have a secondary drive letter although I could create one or connect a disk via USB (because I have old HDD disks from other computers who are not working so I use their disks as storage disks)

About the new account I created it

Here it is

And yes, unfortunately even there the same error happens :/

And about the windows update logs I only see this ones WindowsUpdate.20230609.162719.528.294.zip (From today)

I think you did things correctly, but some ETL files didn't convert correctly.

The WindowsUpdate.log shows entries from 2023/06/09 17:30 to 2023/06/09 17:34, whereas the ProcMon log entries start from 2023/06/09 16:29 PM and end at 2023/06/09 16:31 PM.

That probably means the WindowsUpdate.20230609.162719*.ETL didn't convert correctly. If possible, upload those ETLs if they're still available.

To verify that, I ran a trace on my computer, the ProcMon timestamp and WU log timestamps match exactly. So, some of your ETL files didn't convert.

(The CBS logs look fine. This is not a CBS issue, only a WU/Appx settings issue.)

Try:

• Open Settings → System → Storage → Advanced Storage settings → Where new content is saved.
• Change the "New apps will save to:" and choose a secondary drive letter -- e.g., *D:*

• Open Store and install a new app.

Do you still get the error 80070002?

If so, can you check if this error occurs in other user profile(s)? Please create a new local account to test.

//and if you want I can make and send you another PML file with process monitor from today including the new .ETL files when they will generate so you can correlate the data or do what you are doing to find the problem/

Yes, that would be helpful.

1. Start a Procmon trace.
2. Try to update a Store app and let it fail.
3. Stop the trace.
4. Save all events to a PML file.
5. Zip the PML log (zipping reduces the file size by 90%)
6. Run "get-windowsupdatelog" from PowerShell admin and upload windowsupdate.log (saved to desktop)

(If Step 6 doesn't work, upload all ETL files.)

7. Zip the contents of "c:\windows\Logs\CBS" and upload it.

Thanks.

Thank you, here is the .pml file zipped Logfile.zip

And after running get-windowsupdatelog I got this

And here is the file WindowsUpdate.log

In windows>logs>cbs I found this

So I zipped them and here they are CBS.zip

I hope for your answer, and thank you, have a good day.

//and if you want I can make and send you another PML file with process monitor from today including the new .ETL files when they will generate so you can correlate the data or do what you are doing to find the problem/

Yes, that would be helpful.

1. Start a Procmon trace.
2. Try to update a Store app and let it fail.
3. Stop the trace.
4. Save all events to a PML file.
5. Zip the PML log (zipping reduces the file size by 90%)
6. Run "get-windowsupdatelog" from PowerShell admin and upload windowsupdate.log (saved to desktop)

(If Step 6 doesn't work, upload all ETL files.)

7. Zip the contents of "c:\windows\Logs\CBS" and upload it.

Thanks.

Can you upload the newer ETL files generated on 6/6/2023 and later (other than the 39 files)? Because the ProcMon timestamp is 6:52 so I need the corresponding ETL files to correlate the data. Also, your timezone info can be helpful.

Some important entries from the ETL.

2023/06/07 05:15:18.3111031 3312 7712 Handler *FAILED* [80070002] Failed to get the download volume for the appx update 0D2F00B3-125B-43AE-8C7D-BEF90ACDCD28.1

2023/06/07 05:15:18.3111063 3312 7712 DownloadManager *FAILED* [80070002] Failed to select a download volume for update 0D2F00B3-125B-43AE-8C7D-BEF90ACDCD28

2023/06/07 05:15:18.3111120 3312 7712 DownloadManager *FAILED* [80070002] Failed to initialize the download volume for the updates in the call [{29C5DBC1-CF5B-441F-B1CE-34731FD5AACC}]

Good evening, this is my time and time zone

(Central US and Canada)

Currently I am using the Texas time because there I live.

And about the ETL files I only see this ones in the folder:

so here they are WindowsUpdate.20230608.133338.142.192.zip

and if you want I can make and send you another PML file with process monitor from today including the new .ETL files when they will generate so you can correlate the data or do what you are doing to find the problem (also I would like to thank you for that, I know that is hard and I appreciate your help) although I don´t know why do the files disappear and replace everyday.

Have a good day