[SOLVED] [10v1607b14393 x64] Can't upgrade to 1703/1709. No any new driver (0x800703f1)

[BrianDrab]

Please do the following.

Using File Explorer, navigate to C:\Users\Keiner\AppData\Local.
Rename TileDataLayer to TileDataLayer-old
Using File Explorer, navigate to C:\Users\sysnative\AppData\Local.
Right click and copy TileDataLayer then navigate to C:\Users\Keiner\AppData\Local.
Right click and Paste.

That should have copied the TileDataLayer folder from sysnative to your normal account. The original should still be there as TileDataLayer-old.

Let me know when complete.

 

[ololo]

Unfortunately, sysnative does not have a TileDataLayer directory. (The start menu does not work as 'sysnative' user either)

 

[BrianDrab]

OK, please do the following and let me know when complete.

1. Ensure you copy FRST64.exe on to your USB drive.
2. Also place the attached file on to the USB drive.
3. Reboot into Advanced Options and get to the Command-Prompt
4. Plug in the USB drive into the computer
5. Get to the USB drive. If the USB drive got mapped as D: for example then you can type D: and hit enter
6. Once you are at the prompt representing the usb drive, type frst64 and hit enter.
7. FRST will open. Click fix to perform the fix.
8. Once the fix is done, reboot your computer normally and sign in with the sysnative user.

 

[ololo]

Now, login takes long again :), black screen and so on.

 

[BrianDrab]

OK, I have several more ideas. Please do the following again.

1. Ensure you copy FRST64.exe on to your USB drive.
2. Also place the attached file on to the USB drive.
3. Reboot into Advanced Options and get to the Command-Prompt
4. Plug in the USB drive into the computer
5. Get to the USB drive. If the USB drive got mapped as D: for example then you can type D: and hit enter
6. Once you are at the prompt representing the usb drive, type frst64 and hit enter.
7. FRST will open. Click fix to perform the fix.
8. Once the fix is done, reboot your computer normally and sign in with the sysnative user.

 

[ololo]

Done. Delays for task manager or command prompt are gone but desktop and taskbar still take long.

 

[BrianDrab]

Please open up a powershell command-prompt as administrator.

Copy / Paste the following command in the Administrator: Windows PowerShell window and press Enter key:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

Let me know when this is complete.

 

[ololo]

I get:

Get-AppXPackage : The dependency service or group failed to start.
The dependency service or group failed to start.
At line:1 char:1
+ Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopm ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-AppxPackage], Exception
    + FullyQualifiedErrorId : System.Exception,Microsoft.Windows.Appx.PackageManager.Commands.GetAppxPackageCommand

Probably that's because we disabled the StateRepository service?

Btw: Somebody here seems to have similar problems (last answer):
windows 10 start button. (get-appxpackage also not working in - Microsoft Community

 

[ololo]

Wow I got it to work!

One step I performed was renaming TileDataLayer in my user's directory so it would be recreated. I don't think this is what helped though.

What did it, I believe, was following Crantex' advice from the thread I posted in my last message even though he had somewhat different symptoms:

Fix was suggested by this url: Using PowerShell to resolve Sysprep problems involving App-X packages - TechGenix
which basically says to rename the state repository database files and windows will recreate them properly...
Rather than set up a scheduled task as described there I rebooted my machine into a command prompt (not safe mode but a command prompt) and renamed the following files:-


C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd
C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd-shm
C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd-wal
C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Machine.srd
C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Machine.srd-shm
C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Machine.srd-wal


e.g. C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment.srd renamed to C:\ProgramData\Microsoft\Windows\AppRepository\StateRepository-Deployment-Corrupted.srd

then rebooted my machine into normal mode. Bingo - windows recreated the database files and started updating again...

so far so good...

After that I enabled the StateRepository service via registry again and rebooted. The following login was as quick as can be.

Many thanks to everyone involved in this thread, especially to you, Brian. Without your relentlessness I would have never done it :) I'll be sure to donate soon. Do you somehow get your share of donations or is it all volunteer-based work here?

 

[BrianDrab]

Excellent work and thank you for letting me know!!!! All of our help is volunteer based. The donations to the site keep in chugging along however so thank you.

 

[Sysnative Windows Update]

Glad to see this has been resolved!