Page 7 of 7 First ... 34567
  1. #121
    Administrator
    Windows Update Instructor
    Security Analyst

    Join Date
    Oct 2014
    Posts
    17,098

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

    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.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #122

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

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

  3. #123
    Administrator
    Windows Update Instructor
    Security Analyst

    Join Date
    Oct 2014
    Posts
    17,098

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

    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.
    Attached Files Attached Files

  4. #124

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

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

  5. #125
    Administrator
    Windows Update Instructor
    Security Analyst

    Join Date
    Oct 2014
    Posts
    17,098

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

    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.
    Attached Files Attached Files

  6. #126

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

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

  7. #127
    Administrator
    Windows Update Instructor
    Security Analyst

    Join Date
    Oct 2014
    Posts
    17,098

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

    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.

  8. #128

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

    I get:
    Code:
    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

  9. #129

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

    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?

  10. #130
    Administrator
    Windows Update Instructor
    Security Analyst

    Join Date
    Oct 2014
    Posts
    17,098

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

    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.

  11. #131
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    8,645
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

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

    Glad to see this has been resolved!
    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

Page 7 of 7 First ... 34567

Similar Threads

  1. Replies: 124
    Last Post: 03-21-2018, 02:58 PM
  2. [SOLVED] [10v1607b14393 x64] WU no longer working
    By bastianr in forum Windows Update
    Replies: 69
    Last Post: 03-09-2018, 06:12 PM
  3. [10v1607b14393 x64] Corrupted components hive
    By freesoul in forum Windows Update
    Replies: 3
    Last Post: 12-15-2017, 04:12 PM
  4. Windows 10 1709 high ISR and DPC latency
    By urik27 in forum Windows 10
    Replies: 0
    Last Post: 10-25-2017, 02:35 PM

Log in

Log in