Nvidia driver install failed win 10 corrupt registry? Error 0x800703f1

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 10
       #1

    Nvidia driver install failed win 10 corrupt registry? Error 0x800703f1


    Hey there last night I went to update my driver and got a driver install failure. So I uninstalled old drivers and other nvidia related software and went to reinstall. After uninstalling the drivers my GPU no longer shows up in device manager, after much trial and error.
    1.Tried ddu and did it again trying old drivers
    2. Tried updating through device manager (scan for hardware changes)
    3. Reseating the GPU
    4. Windows update, the windows update failures led me to an error: 0x800703f1
    5. Tried updating my windows to a newer build version which gave me the "something went wrong" error message.


    After running sfc /scannow I got this message Windows resource protection found corrupt files but was unable to fix some of them. I have a log for it but I have no idea how to read it. If anyone could please help. I have sunk 12 hours into this problem since last night and want this nightmare to be over.

    i5-2500
    8 GB Kingston
    GTX 1060 3GB
    Asrock z75 pro3
    Corsair tx650


    Here is the log information


    2017-04-08 10:08:43, Info CBS CbsCoreFinalize: AppContainerUnload
    2017-04-08 10:08:43, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
    2017-04-08 10:08:43, Info CBS Ending TiWorker finalization.
    2017-04-08 10:08:43, Info CBS Ending the TrustedInstaller main loop.
    2017-04-08 10:08:43, Info CBS Starting TrustedInstaller finalization.
    2017-04-08 10:08:43, Info CBS Ending TrustedInstaller finalization.
    2017-04-08 10:23:19, Info CBS TI: --- Initializing Trusted Installer ---
    2017-04-08 10:23:19, Info CBS TI: Last boot time: 2017-04-08 10:20:38.491
    2017-04-08 10:23:20, Info CBS Starting TrustedInstaller initialization.
    2017-04-08 10:23:20, Info CBS Ending TrustedInstaller initialization.
    2017-04-08 10:23:20, Info CBS Starting the TrustedInstaller main loop.
    2017-04-08 10:23:20, Info CBS TrustedInstaller service starts successfully.
    2017-04-08 10:23:20, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2017-04-08 10:23:20, Info CBS Startup processing thread terminated normally
    2017-04-08 10:23:20, Info CBS TI: Startup Processing completes, release startup processing lock.
    2017-04-08 10:23:20, Info CBS Starting TiWorker initialization.
    2017-04-08 10:23:20, Info CBS Ending TiWorker initialization.
    2017-04-08 10:23:20, Info CBS Starting the TiWorker main loop.
    2017-04-08 10:23:20, Info CBS TiWorker starts successfully.
    2017-04-08 10:23:20, Info CBS Universal Time is: 2017-04-08 17:23:20.483
    2017-04-08 10:23:20, Info CBS Loaded Servicing Stack v10.0.14393.1051 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.1051_none_7f2bf7ea21d201b2\cbscore.dll
    2017-04-08 10:23:20, Info CSI 00000001@2017/4/8:17:23:20.639 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fff23816c69 @0x7fff23be55bb @0x7fff23be6372 @0x7ff750bb2d9d @0x7ff750bb35e0 @0x7fff389f7de3)
    2017-04-08 10:23:20, Info CBS NonStart: Set pending store consistency check.
    2017-04-08 10:23:20, Info CBS Session: 30584972_3518568457 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2017-04-08 10:23:20, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-04-08 10:23:20, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2017-04-08 10:23:20, Info CBS Session: 30584972_3518568458 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    2017-04-08 10:23:20, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2017-04-08 10:23:20, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{92EC2FD0-E6D7-4983-9685-02789AFB5C86}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{6B1BDF42-539B-4C6F-AD6C-727D06B404E1}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Fonts-Hans-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{D063A4FB-E8B6-43A5-9ECC-C9301EDC15DB}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Handwriting-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{FC6EE896-D5CA-4313-B831-445B27605F79}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-OCR-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{4C36A54F-50BC-4588-AA8B-9B69801BFFA3}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Speech-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{32EF2A88-2C6B-4786-B0FD-88537EC7918D}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-TextToSpeech-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{56B3B446-8274-4CB5-8931-4D75D10FB068}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-nso-za-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{81F12E4E-4A85-4492-8633-1F5385501B10}, revision: 203
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-Merged~31bf3856ad364e35~amd64~ro-RO~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{09556823-3DDB-439B-AF0F-75F06B03163C}, revision: 202
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-Merged~31bf3856ad364e35~amd64~ug-CN~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{9B8E8CB8-DF03-44D4-88BD-B5C73A99D1BD}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-sr-cyrl-rs-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{21741B0D-AC5A-4FD7-B7A0-77354955F717}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Handwriting-sr-cyrl-rs-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{13A5CBD7-78B8-4F23-9613-39345047FE53}, revision: 202
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-Merged~31bf3856ad364e35~amd64~sr-LATN-RS~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{3E74763E-67B2-40C4-A753-2A02FA285C28}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LIP-LanguagePack-Package~31bf3856ad364e35~amd64~ky-KG~10.0.14393.0, ApplicableState: 112, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{7FABC6E3-818F-4285-A3B8-BC8A3FE5C3F5}, revision: 202
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-ua~31bf3856ad364e35~amd64~~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{072FDD9C-11AA-419B-88A4-1C60E0268F15}, revision: 200
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Package_for_KB3072073~31bf3856ad364e35~amd64~~10.0.1.1, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Mapping_Package_for_KB3089226_af-ZA_amd64~31bf3856ad364e35~amd64~~10.0.10240.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{D27A15A8-AB96-4C7A-8490-69320437F767}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~es-ES~10.0.14393.0, ApplicableState: 112, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{63A5AA71-438F-4A73-AEE7-872C11A79248}, revision: 205
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-Merged~31bf3856ad364e35~amd64~sw-KE~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{8ABF0E84-C645-4CB8-B7CA-6314D86BDFF4}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LIP-LanguagePack-Package~31bf3856ad364e35~amd64~ga-IE~10.0.14393.0, ApplicableState: 112, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{EA1C6660-8600-4DD8-A245-A31763328CEA}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-yo-ng-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{4B857F1A-0C0B-4F6E-BA81-040C6286B2D2}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-bs-latn-ba-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{A971E800-BC5A-4D6D-BC4D-9E4AC4D0B551}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Handwriting-bs-latn-ba-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{B9C82C13-8972-42D8-96E9-EBAB3D67E924}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-OCR-bs-latn-ba-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{93A36601-F459-43B3-B386-885669888110}, revision: 204
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-avcore~31bf3856ad364e35~amd64~~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{6261FEEA-5B19-4A49-9575-35ECA9C322AB}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-ms-my-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{E0DC92C7-B9AE-48E7-8DBE-7EBD98B7443E}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Handwriting-ms-my-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{F534C8B0-9798-49EE-87D9-5A5272F379AF}, revision: 200
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-Merged~31bf3856ad364e35~amd64~ru-RU~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{F60EE4FE-AD5C-4873-BA12-0CDF9C9A3105}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LIP-LanguagePack-Package~31bf3856ad364e35~amd64~rw-RW~10.0.14393.0, ApplicableState: 112, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{4192EB2C-1534-4A26-AFD9-5A7AD20B6771}, revision: 200
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0, ApplicableState: 112, CurrentState:112
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{4172D5A8-2756-4B59-9482-9C7316551C02}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Package_for_KB3051768~31bf3856ad364e35~amd64~~10.0.1.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{17CDAF78-E953-410C-889C-766DAD1E613F}, revision: 201
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LIP-LanguagePack-Package~31bf3856ad364e35~amd64~pa-IN~10.0.14393.0, ApplicableState: 112, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{390770F4-3986-46D7-A17E-865E25775A1C}, revision: 202
    2017-04-08 10:23:23, Info CBS Read out cached applicability from TiLight for package: KB3089226-Merged~31bf3856ad364e35~amd64~quz-PE~10.0.10586.0, ApplicableState: 0, CurrentState:0
    2017-04-08 10:23:23, Info CBS WU creates the package, AppID evice Driver Retrieval Client, UpdateID:{52780322-F7F4-4455-B96A-1CAFC2FF2BBE}, revision: 200



    Just ran DISM in command prompt

    DISM /Online /Cleanup-Image /RestoreHealth

    After reaching 100% it says

    Error: 0x800f081f

    The source files could not be found
    Use the "source" option to specify the location of the files that are required to restore the feature.


    Alright just about the only thing I really do on this PC is yes, you guessed it play WoW. I actually couldn't lead my raid tonight because of this issue :[ so my question is if I use the Reset this PC feature under the recovery options and choose to keep my files will this
    1Fix my corrupted windows registry and get my PC to detect my GPU?
    2. Allow me to download the new Nvidia driver,
    3 All without having to reinstall WoW?


    Also thanks ahead of time for any help/answers!




      My Computer


  2. TV2
    Posts : 2,221
    W10 Pro 22H2
       #2

    How, specifically, did you "uninstalled old drivers and other nvidia related software"?

    Do you have a System Restore Point that is dated before you started trying to fix the problem?
    You might try a System Restore before a reset.

    Have you tried to install the newest nVidia driver package, choose custom installation, and check the box for "Perform a clean installation"?
      My Computers


  3. Posts : 5
    Windows 10
    Thread Starter
       #3

    I uninstalled them manually. From the control panel.
    Yes system restore does absolutely nothing an error is caused from %programfiles% windows appxstaging.
    Also yes I downloaded the newest driver and did a clean install. This is exactly what DDU is and yes I did it myself and via the program.
      My Computer


  4. Posts : 5
    Windows 10
    Thread Starter
       #4

    Tried running this Start fresh with a clean installation of Windows 10 and got a 0x8007043c-0x90016 error. Pretty sure the problem is corrupted OS registry.
      My Computer


  5. Posts : 5
    Windows 10
    Thread Starter
       #5

    Ok so just to cover what ive done and what has happened since this morning. If you need to run anything else, upload any more logs/pic please ask.

    Went to device manager>Other devices>Unknown device>Right click>Update driver software
    1. When I click auto I get this https://i.imgur.com/cV62Yos.jpg

    2 When I click manual> specify driver location (The driver files did not show up)
    2A. When I click manual> let me pick from list> specify the device as a displayer adapter>pick microsoft basic display adapter for the driver and I get https://i.imgur.com/v4OCu2x.jpg

    3. When I go to recovery>reset this pc> remove all files> remove files + clean drive I get: https://i.imgur.com/koWTqyL.jpg

    4. When I go to advanced restart> reset this pc> remove all files and clean drive I get
    https://i.imgur.com/SzmyjrB.jpg

    5. I ran startup repair while I was in that menu and go: https://i.imgur.com/ooFNClE.jpg
    (I will find the log to upload in case someone who can read it visits this post)

    6. I saw this on the option I didn't run it but was wondering if it could help
    https://i.imgur.com/O2ADPIx.jpg
      My Computer


  6. Posts : 5
    Windows 10
    Thread Starter
       #6

    Here is the log for startup repair process.

    Startup Repair diagnosis and repair log
    ---------------------------
    Last successful boot time: ‎4/‎9/‎2017 5:40:41 PM (GMT)
    Number of repair attempts: 1

    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = D:\WINDOWS
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 313 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 93 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code = 0x0
    Time taken = 79 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code = 0x0
    Time taken = 27359 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 62 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 63 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code = 0x0
    Time taken = 16 ms

    Test Performed:
    ---------------------------
    Name: Setup state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 421 ms

    Test Performed:
    ---------------------------
    Name: Registry hives test
    Result: Completed successfully. Error code = 0x0
    Time taken = 3485 ms

    Test Performed:
    ---------------------------
    Name: Windows boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Bugcheck analysis
    Result: Completed successfully. Error code = 0x0
    Time taken = 906 ms

    Test Performed:
    ---------------------------
    Name: Access control test
    Result: Completed successfully. Error code = 0x0
    Time taken = 21687 ms

    Test Performed:
    ---------------------------
    Name: File system test (chkdsk)
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Software installation log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Fallback diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Root cause found:
    ---------------------------
    Unspecified changes to system configuration might have caused the problem.

    Repair action:
    Result: Failed. Error code = 0x32
    Time taken = 766 ms

    Repair action: System Restore
    Result: Failed. Error code = 0x1f
    Time taken = 1534078 ms

    Repair action: System files integrity check and repair
    Result: Failed. Error code = 0x490
    Time taken = 1276578 ms

    ---------------------------
    ---------------------------
      My Computer


  7. Posts : 2,550
    Windows 10 Pro 64bit
       #7

    Same here, I deleted the nVidia drivers & the nVidia GeForce experience, I then reinstalled the GeForce experience from a saved download & installed the driver, all now working.
      My Computer


  8. Posts : 374
    Windows 10-64 bit (version 1909 build 18363.628)
       #8

    Bastet said:
    Same here, I deleted the nVidia drivers & the nVidia GeForce experience, I then reinstalled the GeForce experience from a saved download & installed the driver, all now working.
    How did you uninstall those drivers? I used display driver uninstaller but I'm having issues in installation of nVidia GeForce GTX 1050Ti drivers.

    The installation fails.

    If I use device manager, I get the error ""The configuration registry database is corrupt"
      My Computer


  9. Posts : 26,450
    Windows 11 Pro 22631.3447
       #9

    tbrown37 said:
    Here is the log for startup repair process.

    Startup Repair diagnosis and repair log
    ---------------------------
    Last successful boot time: ‎4/‎9/‎2017 5:40:41 PM (GMT)
    Number of repair attempts: 1

    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory = D:\WINDOWS
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 313 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code = 0x0
    Time taken = 93 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code = 0x0
    Time taken = 79 ms

    Test Performed:
    ---------------------------
    Name: Volume content check
    Result: Completed successfully. Error code = 0x0
    Time taken = 27359 ms

    Test Performed:
    ---------------------------
    Name: Boot manager diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 62 ms

    Test Performed:
    ---------------------------
    Name: System boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Event log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 63 ms

    Test Performed:
    ---------------------------
    Name: Internal state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Boot status test
    Result: Completed successfully. Error code = 0x0
    Time taken = 16 ms

    Test Performed:
    ---------------------------
    Name: Setup state check
    Result: Completed successfully. Error code = 0x0
    Time taken = 421 ms

    Test Performed:
    ---------------------------
    Name: Registry hives test
    Result: Completed successfully. Error code = 0x0
    Time taken = 3485 ms

    Test Performed:
    ---------------------------
    Name: Windows boot log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Bugcheck analysis
    Result: Completed successfully. Error code = 0x0
    Time taken = 906 ms

    Test Performed:
    ---------------------------
    Name: Access control test
    Result: Completed successfully. Error code = 0x0
    Time taken = 21687 ms

    Test Performed:
    ---------------------------
    Name: File system test (chkdsk)
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Software installation log diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Fallback diagnosis
    Result: Completed successfully. Error code = 0x0
    Time taken = 0 ms

    Root cause found:
    ---------------------------
    Unspecified changes to system configuration might have caused the problem.

    Repair action:
    Result: Failed. Error code = 0x32
    Time taken = 766 ms

    Repair action: System Restore
    Result: Failed. Error code = 0x1f
    Time taken = 1534078 ms

    Repair action: System files integrity check and repair
    Result: Failed. Error code = 0x490
    Time taken = 1276578 ms

    ---------------------------
    ---------------------------
    Your post is very hard to read using The Dark Wide theme.
      My Computer


  10. Posts : 26,450
    Windows 11 Pro 22631.3447
       #10

    archz2 said:
    How did you uninstall those drivers? I used display driver uninstaller but I'm having issues in installation of nVidia GeForce GTX 1050Ti drivers.

    The installation fails.

    If I use device manager, I get the error ""The configuration registry database is corrupt"
    Use DDU in Safe mode and turn of Windows Safe Screen or whatever it is called. After reboot from Safe mode pull your Ethernet cable or disable your network.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:35.
Find Us




Windows 10 Forums