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

ololo

Well-known member
Joined
Jan 12, 2018
Posts
68
Hello,

I've come to this forum as the quality of answers in previous Windows problem threads was very high and I found valueable insight already. I still cannot fix the problem I'm having with my Windows 10:

Recently, perhaps two months ago, my printer driver stopped working, I presume this was triggered by a Windows update. On other computers accessing the same printer, this issue was also present but got resolved after updating to the 1709 version.

Digging a little deeper I realized that this Windows already failed to install the 1703 update but apparently was not as persistent as it is now in nagging me with update notifications. The situation is that Windows Update attempts to download the update (5 hours via my slow connection), installs it, fails and reverts and promptly downloads the update again for a new try. Not only does this clog my connection but I feel it's becoming a more serious problem now with the printer not working and maybe other hardware in future.

I followed the usual advice like
Code:
sfc /scannow
or reverting the DISM image as well as other hints from everywhere but nothing helped.
An in-place update (per Media Creation Tool) fails as well as reverting to an old snapshot. Resetting the COMPONENTs did not help or I performed it incorrectly.

Analyzing the update log (CBS) showed that apparently the update fails when updating a driver as seen in the relevant snippet from the log. Can provide more if requested.

Code:
2018-01-02 20:32:38, Info                  CBS    Perf: Doqe: Staging started.
2018-01-02 20:32:38, Info                  CBS    Doqe: [Forward] Staging driver updates, Count 43
2018-01-02 20:32:39, Info                  CBS            STAGE index: 28, phase: 1, result 1009, inf: miradisp.inf
2018-01-02 20:32:39, Info                  CBS    Doqe: Recording result: 0x800703f1, for Inf: miradisp.inf
2018-01-02 20:32:39, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x800703f1 - ERROR_BADDB]
2018-01-02 20:32:39, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]
2018-01-02 20:32:39, Info                  CBS    Perf: Doqe: Staging ended.
2018-01-02 20:32:39, Error                 CBS    Failed staging drivers, rebooting and trying again [HRESULT = 0x800703f1 - ERROR_BADDB]

I never used the miradisp driver and I have no Miracast device at all but it seems to be packaged with Windows by default.

I suspect the registry or parts of it are corrupt but I have no idea how to fix it. I've come here as last resort basically, since I'm out of ideas. I fixed a lot of Windows problems but my knowledge is too limited to continue here. Even though, I'd really like to keep this installation as a full reinstall with all applications would take me days. Is there any hope?
 
Re: Windows 10 does not install 1709, 1703 Updates nor any new driver (0x800703f1)

Hi xilolee,

thanks for moving the topic to the proper place.

It's an AMD A6-7400K with integrated Radeon GPU, mainboard ASrock FM2A58M-DG3+. Apart from that, there's not much in it, 1 TB HDD and a smart card reader.

I don't have any antivirus active apart from Windows defender and I'm not using any encryption scheme.

Edit: Ah, almost forgot, currently the Windows version is 1610, apparently no newer larger update went through.
 
Re: [10v1703b15063 x64] Can't upgrade to 1709. No any new driver (0x800703f1)

1610 should be an insider build, if I'm not wrong (or it doesn't exist at all...).
 
Last edited:
Re: [10v1610 ? x64] Can't upgrade to 1703/1709. No any new driver (0x800703f1)

Arg, you're right of course. I got it mixed up with Ubuntu :) winver says: 1607 (OS Build 14393.222)

I'm apparently too tired to read or write, 14393 not 14392, please apologize.
CBS.log is attached.
 

Attachments

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

Excuse my sloppiness, updated the previous post.

In addition, Here is the sfcfix output:

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-12 21:23:30.330
Microsoft Windows 10 Build 14393 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-01-12 21:32:10.301
----------------------EOF-----------------------

and the dism output:
Code:
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

Image Version: 10.0.14393.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 
Attached. (This log seems interesting btw)

It seems as if there was an error installing the smart card reader driver. This device is currently not attached. It fits the general description that no drivers at all can be installed though.
 

Attachments

It's a SCM SCR3310, uninstalling the driver should be possible. (Provided we can fix the driver installation issue)
The manufacturer website is:
SCM PC-Card GmbH - SCR3310

Where do I get the Hardware ID from?

Hardware IDs in its device properties says:
USB\VID_04E6&PID_5116&REV_0304
USB\VID_04E6&PID_5116

If this is the information you need, I can uninstall it.
 
No success, setupapi.dev.log still shows errors installing this driver (as well as a screen driver of a screen I had attached a week ago).
Device manager is "clean" now, though, as I have disconnected the smart card reader.

Attached new logs.
 

Attachments

Hi -

softwaremaniac has asked that I jump in and assist as he will be unavailable for a little. Please start with the following.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Results:

Code:
Fix result of Farbar Recovery Scan Tool (x64) Version: 14.01.2018
Ran by Keiner (14-01-2018 18:15:06) Run:1
Running from C:\Users\Keiner\Desktop
Loaded Profiles: Keiner (Available Profiles: Keiner)
Boot Mode: Normal
==============================================

fixlist content:
*****************
C:\windows\system32\config\drivers
*****************

C:\windows\system32\config\drivers => moved successfully

==== End of Fixlog 18:15:06 ====
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top