[SOLVED] [W10v1507b10240] WU Error 0x800703f1

Re: Windows update problem Error Code 0x800703f1

JcJ91sx.png
GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:


  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, copy and paste their name in your next reply (or take a screenshot of the GSmartControl window and attach it in your next reply);
    info_failing.png
 
Re: Windows update problem Error Code 0x800703f1

"Test #","Type","Status","% Completed","Lifetime hours","LBA of the first error"1,"Extended offline","Manually aborted","30%","3180","-"

PINK CELLS FROM ATTRIBUTES TAB:
"ID","Name","Failed","Norm-ed value","Worst","Threshold","Raw value","Type","Flags"
196,"Reallocation Event Count","never","97","97","30","2937 (40872 0)","<b>pre-failure</b>","POSR--"
 
Re: Windows update problem Error Code 0x800703f1

It appears that your hard drive is failing, we can try to repair the current issues, but please bear in mind that your HDD may fail very soon and it may continue to work for years to come. There's no way of knowing for sure.

chkdsk /r

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /r
  4. Reboot
  5. Download ListChkdskResult.exe (by SleepyDude) from the link below:

    https://dl.dropboxusercontent.com/u/...kdskResult.exe
  6. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!
 
Re: Windows update problem Error Code 0x800703f1

I keep getting this message, despite closing all windows and rebooting, then running command again:

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
 
Re: Windows update problem Error Code 0x800703f1

I was able to run the chkdsk command as requested but the scan and repair process gets stuck at 11%. It has been stuck there for over an hour. Any idea how to exit the scan and repair process?

LABeagle said:
I keep getting this message, despite closing all windows and rebooting, then running command again:

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Click to expand...
 
Re: Windows update problem Error Code 0x800703f1

No worries. I entered "Y" to repair on startup and when I re-start, the repair begins but I am unable to get past 11%. It gets stuck and I have to reboot and exit the repair process when the computer re-starts.

softwaremaniac said:
Sorry for the delay. Were you able to complete the process?
Click to expand...
 
Re: Windows update problem Error Code 0x800703f1

Please do it again and leave it running at least overnight. It would be ideal if you could leave the test on for even longer.
 
Re: Windows update problem Error Code 0x800703f1

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013


------< Log generate on 11/3/2017 6:56:47 PM >------
Category: 0
Computer Name: ChrisPC
Event Code: 1001
Record Number: 104977
Source Name: Microsoft-Windows-Wininit
Time Written: 11-03-2017 @ 22:00:21
Event Type: Information
User:
Message:


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


A disk check has been scheduled.
Windows will now check the disk.


Stage 1: Examining basic file system structure ...
392448 file records processed.


File verification completed.
21944 large file records processed.


0 bad file records processed.




Stage 2: Examining file name linkage ...
485334 index entries processed.


Index verification completed.
0 unindexed files scanned.


0 unindexed files recovered to lost and found.




Stage 3: Examining security descriptors ...
Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
46444 data files processed.


CHKDSK is verifying Usn Journal...
32266944 USN bytes processed.


Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
392432 files processed.


File data verification completed.


Stage 5: Looking for bad, free clusters ...
59007415 free clusters processed.


Free space verification is complete.


Windows has scanned the file system and found no problems.
No further action is required.


465685503 KB total disk space.
228982252 KB in 230594 files.
159900 KB in 46445 indexes.
0 KB in bad sectors.
513691 KB in use by the system.
65536 KB occupied by the log file.
236029660 KB available on disk.


4096 bytes in each allocation unit.
116421375 total allocation units on disk.
59007415 allocation units available on disk.


Internal Info:
00 fd 05 00 1b 36 04 00 e4 4a 08 00 00 00 00 00 .....6...J......
8c 23 00 00 48 00 00 00 00 00 00 00 00 00 00 00 .#..H...........


Windows has finished checking your disk.
Please wait while your computer restarts.


-----------------------------------------------------------------------
Category: 0
Computer Name: ChrisPC
Event Code: 26212
Record Number: 104889
Source Name: Chkdsk
Time Written: 11-01-2017 @ 16:33:27
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


Stage 1: Examining basic file system structure ...


392448 file records processed.


File verification completed.


21943 large file records processed.




0 bad file records processed.




Stage 2: Examining file name linkage ...


485332 index entries processed.


Index verification completed.


0 unindexed files scanned.




0 unindexed files recovered to lost and found.




Stage 3: Examining security descriptors ...
Security descriptor verification completed.


46443 data files processed.


CHKDSK is verifying Usn Journal...


29504224 USN bytes processed.


Usn Journal verification completed.


Windows has scanned the file system and found no problems.
No further action is required.


465685503 KB total disk space.
231640760 KB in 230763 files.
159940 KB in 46444 indexes.
0 KB in bad sectors.
511063 KB in use by the system.
65536 KB occupied by the log file.
233373740 KB available on disk.


4096 bytes in each allocation unit.
116421375 total allocation units on disk.
58343435 allocation units available on disk.


-----------------------------------------------------------------------
Category: 0
Computer Name: ChrisPC
Event Code: 26212
Record Number: 104805
Source Name: Chkdsk
Time Written: 10-31-2017 @ 21:29:11
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.


Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


Stage 1: Examining basic file system structure ...


392448 file records processed.


File verification completed.


22008 large file records processed.




0 bad file records processed.




Stage 2: Examining file name linkage ...
The file name attributes in file 0x59880 has different parents.
The DOS name has 0x300000005987f as parent. The NTFS name has 0xc00000000d3d6 as parent.

Minor file name errors were detected in file 366720.
Unable to locate the file name attribute of index entry RE3C37~1.ETL
of index $I30 with parent 0x2af6 in file 0x357af.

Index entry RE3C37~1.ETL in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry REBB37~1.ETL
of index $I30 with parent 0x2af6 in file 0x3361f.
Index entry REBB37~1.ETL in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry RECC9B~1.ETL
of index $I30 with parent 0x2af6 in file 0x236b9.
Index entry RECC9B~1.ETL in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry Remediation.026.etl
of index $I30 with parent 0x2af6 in file 0x236b9.
Index entry Remediation.026.etl in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry Remediation.041.etl
of index $I30 with parent 0x2af6 in file 0x357af.
Index entry Remediation.041.etl in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry Remediation.044.etl
of index $I30 with parent 0x2af6 in file 0x3361f.
Index entry Remediation.044.etl in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry Remediation.050.etl
of index $I30 with parent 0x2af6 in file 0x25249.
Index entry Remediation.050.etl in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry REMEDI~1.ETL
of index $I30 with parent 0x2af6 in file 0x25249.
Index entry REMEDI~1.ETL in index $I30 of file 10998 is incorrect.
Unable to locate the file name attribute of index entry PACKAG~1.MUM
of index $I30 with parent 0xd3d6 in file 0x59880.

Index entry PACKAG~1.MUM in index $I30 of file 54230 is incorrect.
Unable to locate the file name attribute of index entry NO0506~1.ETL
of index $I30 with parent 0x3fa8c in file 0x27a7f.

Index entry NO0506~1.ETL in index $I30 of file 260748 is incorrect.
Unable to locate the file name attribute of index entry NO2562~1.ETL
of index $I30 with parent 0x3fa8c in file 0x2556a.
Index entry NO2562~1.ETL in index $I30 of file 260748 is incorrect.
Unable to locate the file name attribute of index entry NO9DA4~1.ETL
of index $I30 with parent 0x3fa8c in file 0x2cd6d.
Index entry NO9DA4~1.ETL in index $I30 of file 260748 is incorrect.
Unable to locate the file name attribute of index entry NOBFC1~1.ETL
of index $I30 with parent 0x3fa8c in file 0x26fb6.
Index entry NOBFC1~1.ETL in index $I30 of file 260748 is incorrect.
Unable to locate the file name attribute of index entry NODAD5~1.ETL
of index $I30 with parent 0x3fa8c in file 0x27a7d.
Index entry NODAD5~1.ETL in index $I30 of file 260748 is incorrect.
Unable to locate the file name attribute of index entry NOE2E8~1.ETL
of index $I30 with parent 0x3fa8c in file 0x2cd6a.
Index entry NOE2E8~1.ETL in index $I30 of file 260748 is incorrect.


485236 index entries processed.


Index verification completed.


Errors found. CHKDSK cannot continue in read-only mode.


-----------------------------------------------------------------------
Category: 0
Computer Name: ChrisPC
Event Code: 26228
Record Number: 104628
Source Name: Chkdsk
Time Written: 10-21-2017 @ 22:59:25
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.


Checking file system on \Device\HarddiskVolume4
Volume label is OS.


Examining 8 corruption records ...


Record 1 of 8: Corrupt File "\ProgramData\USOShared\Logs\NotificationUxBroker.064.etl <0x3f,0x2556a>" ... no corruption found.


Record 2 of 8: Unneeded index entry in index "$I30" of directory "\ProgramData\USOShared\Logs <0x4,0x3fa8c>" ... no corruption found.


Record 3 of 8: Corrupt File "\ProgramData\USOShared\Logs\NotificationUxBroker.060.etl <0x8a,0x26fb6>" ... no corruption found.


Record 4 of 8: Unneeded index entry in index "$I30" of directory "\ProgramData\USOShared\Logs <0x4,0x3fa8c>" ... no corruption found.


Record 5 of 8: Corrupt File "\ProgramData\USOShared\Logs\NotificationUxBroker.059.etl <0x36,0x27a7f>" ... no corruption found.


Record 6 of 8: Unneeded index entry in index "$I30" of directory "\ProgramData\USOShared\Logs <0x4,0x3fa8c>" ... no corruption found.


Record 7 of 8: Corrupt File "\ProgramData\USOShared\Logs\NotificationUxBroker.053.etl <0x38,0x27a7d>" ... no corruption found.


Record 8 of 8: Unneeded index entry in index "$I30" of directory "\ProgramData\USOShared\Logs <0x4,0x3fa8c>" ... no corruption found.


8 corruption records processed in 0.2 seconds.


Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.


-----------------------------------------------------------------------
Category: 0
Computer Name: ChrisPC
Event Code: 26228
Record Number: 104627
Source Name: Chkdsk
Time Written: 10-21-2017 @ 22:59:19
Event Type: Information
User:
Message: Chkdsk was executed in verify mode on a volume snapshot.


Checking file system on \Device\HarddiskVolume4
Volume label is OS.


Examining 4 corruption records ...


Record 1 of 4: Corrupt File "\ProgramData\USOShared\Logs\NotificationUxBroker.091.etl <0x23,0x2cd6a>" ... no corruption found.


Record 2 of 4: Unneeded index entry in index "$I30" of directory "\ProgramData\USOShared\Logs <0x4,0x3fa8c>" ... no corruption found.


Record 3 of 4: Corrupt File "\ProgramData\USOShared\Logs\NotificationUxBroker.090.etl <0x24,0x2cd6d>" ... no corruption found.


Record 4 of 4: Unneeded index entry in index "$I30" of directory "\ProgramData\USOShared\Logs <0x4,0x3fa8c>" ... no corruption found.


4 corruption records processed in 0.2 seconds.


Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.


-----------------------------------------------------------------------
Category: 0
Computer Name: ChrisPC
Event Code: 26213
Record Number: 102871
Source Name: Chkdsk
Time Written: 09-20-2017 @ 04:01:57
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode. A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.


Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


Stage 1: Examining basic file system structure ...


376832 file records processed.


File verification completed.


21749 large file records processed.




0 bad file records processed.




Stage 2: Examining file name linkage ...
The file name attributes in file 0x59880 has different parents.
The DOS name has 0x300000005987f as parent. The NTFS name has 0xc00000000d3d6 as parent.

Minor file name errors were detected in file 366720.
The multi-sector header signature for VCN 0x349 of index $I30
in file 0xbf is incorrect.
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? ................

Error detected in index $I30 for file 191.
Index entry AM093D~2.MAN of index $I30 in file 0xbf points to unused file 0x3d946.
Index entry AM093D~2.MAN in index $I30 of file 191 is incorrect.
Index entry AM0A0D~1.MAN of index $I30 in file 0xbf points to unused file 0x3d929.
Index entry AM0A0D~1.MAN in index $I30 of file 191 is incorrect.
Index entry AM13FD~1.MAN of index $I30 in file 0xbf points to unused file 0x3d933.
Index entry AM13FD~1.MAN in index $I30 of file 191 is incorrect.
The file reference 0x34000000005808 of index entry AM20B2~1.MAN of index $I30
with parent 0xbf is not the same as 0x33000000005808.
Index entry AM20B2~1.MAN in index $I30 of file 191 is incorrect.
Index entry AM2122~1.MAN of index $I30 in file 0xbf points to unused file 0x3d909.
Index entry AM2122~1.MAN in index $I30 of file 191 is incorrect.
Index entry AM21AC~3.MAN of index $I30 in file 0xbf points to unused file 0x3d908.
Index entry AM21AC~3.MAN in index $I30 of file 191 is incorrect.
Index entry AM442E~1.MAN of index $I30 in file 0xbf points to unused file 0x3d913.
Index entry AM442E~1.MAN in index $I30 of file 191 is incorrect.
Index entry AM671C~2.MAN of index $I30 in file 0xbf points to unused file 0x3d917.
Index entry AM671C~2.MAN in index $I30 of file 191 is incorrect.
Index entry AM6FA1~1.MAN of index $I30 in file 0xbf points to unused file 0x3d93f.
Index entry AM6FA1~1.MAN in index $I30 of file 191 is incorrect.
Index entry AM700C~2.MAN of index $I30 in file 0xbf points to unused file 0x3d918.
Index entry AM700C~2.MAN in index $I30 of file 191 is incorrect.
Index entry AM784B~1.MAN of index $I30 in file 0xbf points to unused file 0x3d90f.
Index entry AM784B~1.MAN in index $I30 of file 191 is incorrect.
Index entry AMA2B6~1.MAN of index $I30 in file 0xbf points to unused file 0x3d93e.
Index entry AMA2B6~1.MAN in index $I30 of file 191 is incorrect.
Index entry AMAB97~1.MAN of index $I30 in file 0xbf points to unused file 0x3d938.
Index entry AMAB97~1.MAN in index $I30 of file 191 is incorrect.
Index entry AMB53A~1.MAN of index $I30 in file 0xbf points to unused file 0x3d93c.
Index entry AMB53A~1.MAN in index $I30 of file 191 is incorrect.
Index entry AMBDDC~1.MAN of index $I30 in file 0xbf points to unused file 0x3d91b.
Index entry AMBDDC~1.MAN in index $I30 of file 191 is incorrect.
The index entry length is too small for index entry type 0x6.
00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ................
Unable to locate the file name attribute of index entry PACKAG~1.MUM
of index $I30 with parent 0xd3d6 in file 0x59880.

Index entry PACKAG~1.MUM in index $I30 of file 54230 is incorrect.
Index entry CHKDSK.EXE-13847046.pf of index $I30 in file 0x3f3a9 points to unused file 0x3d906.

Index entry CHKDSK.EXE-13847046.pf in index $I30 of file 258985 is incorrect.
Index entry CHKDSK~1.PF of index $I30 in file 0x3f3a9 points to unused file 0x3d906.
Index entry CHKDSK~1.PF in index $I30 of file 258985 is incorrect.
Index entry WID429~1.SQM of index $I30 in file 0x54362 points to unused file 0x3d905.

Index entry WID429~1.SQM in index $I30 of file 344930 is incorrect.
Index entry WindowsLL.wns.11.sqm of index $I30 in file 0x54362 points to unused file 0x3d905.
Index entry WindowsLL.wns.11.sqm in index $I30 of file 344930 is incorrect.


467956 index entries processed.


Index verification completed.


Errors found. CHKDSK cannot continue in read-only mode.


-----------------------------------------------------------------------
 
Re: Windows update problem Error Code 0x800703f1

Please disconnect your HP OfficeJet and completely remove its software/drivers from the system. Afterwards, please use MCT to try upgrading to the latest Windows 10 build as I previously suggessted in Post#8.

Let me know how it goes.
 
Re: Windows update problem Error Code 0x800703f1

Disconnected printer and removed the printer drivers and software and tried MCT again. "Windows failed to Update" was the message I received midway through the installation.

I tried rebooting and using MCT again and received the same message.
 
Re: Windows update problem Error Code 0x800703f1

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.




  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put tags around the log to break up the text.
  9. A file called Logs.zip will be created on your Desktop. Please upload it to your next post.


Note: If the zip file is too big, use a filesharing service of your choice and just provide a link.
 

Attachments

Re: Windows update problem Error Code 0x800703f1

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-11-05 00:05:10.873
Microsoft Windows 10 Build 10240 - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [1]








Zip::
Successfully copied file C:\$Windows.~BT\Sources\panther\miglog.xml to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\$Windows.~BT\Sources\Rollback\setupact.err to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Failed to copy file C:\Windows\inf\setupapi.app.log to zip file at C:\Users\Administrator\Desktop\Logs.zip due to name collision.
Failed to copy file C:\Windows\inf\setupapi.dev.log to zip file at C:\Users\Administrator\Desktop\Logs.zip due to name collision.
Successfully copied file C:\Windows\Logs\MoSetup\BlueBox.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\Windows\memory.dmp to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Failed to copy file C:\Windows\panther\miglog.xml to zip file at C:\Users\Administrator\Desktop\Logs.zip due to name collision.
Successfully copied file C:\Windows\panther\PostApplyPnPList.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\Windows\panther\PreGatherPnPList.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\Windows\Panther\Setupact.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\Windows\panther\setuperr.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Successfully copied file C:\Windows\setupapi.log to zip file at C:\Users\Administrator\Desktop\Logs.zip.
Zip:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-11-05 00:05:57.172
Script hash: hHFwycZI8fGyOCLvTx2SCEO9T3nNb61yZKgAYA8OFqY=
----------------------EOF-----------------------

Link to Logs file...
Dropbox - Logs.zip
 
Re: Windows update problem Error Code 0x800703f1

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Re: Windows update problem Error Code 0x800703f1

Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2017-11-05 11:58:48.748
Microsoft Windows 10 Build 10240 - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]








FileScan:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-11-05 11:59:14.191
Script hash: 8qzO4/PUGTWYWmZWYZniUBksNJj5rsI+fKZZ/4fMtkg=
----------------------EOF-----------------------
 
Re: Windows update problem Error Code 0x800703f1

Search with Farbar Recovery Scan Tool (FRST)



  • Download FRST or FRST64 and save it to the Desktop.
    (Please pick the version that matches your operating system's bit type. If you don't know which version matches your system, try FRST if it says that is not compatible with your OS you have to use FRST64)
  • Open the Command Prompt as Administrator (Tutorial)
  • Type or copy/paste the following command:

Code: 
dism /online /Get-FeatureInfo /FeatureName:TFTP|find "completed"


  • Wait for the command to finish with "The operation completed successfully"
  • Close the window "Administrator: Command Prompt"
  • Execute FRST/FRST64 right click on the icon
    FRST.jpg
    and choose Run as Administrator. Make sure all other windows are closed.
    (When the tool opens for the first time, you must click Yes on the disclaimer.)
    FRST_SearchRegistry.png
  • On the Search box (1) type or copy and paste the following text:

    hpvyt13.inf
  • Press the Search Registry button.
  • Wait for the search to finish FRST will produce a log called (SearchReg.txt) in the same directory the Tool is run from.
  • Please copy and paste the log to your post.
 
Re: Windows update problem Error Code 0x800703f1

Farbar Recovery Scan Tool (x64) Version: 02-11-2017
Ran by Administrator (05-11-2017 20:10:55)
Running from C:\Users\Administrator\Desktop
Boot Mode: Normal


================== Search Registry: "hpvyt13.inf" ===========


[HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\Pnp\CurrentControlSet\Control\DeviceMigration\Devices\SWD\PRINTENUM\WSD-9B85CF27-5DFD-416C-8CCB-B92F069E2427.0034]
"DriverInfName"="hpvyt13.inf"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\HP Officejet Pro 8610]
"InfPath"="C:\WINDOWS\System32\DriverStore\FileRepository\hpvyt13.inf_amd64_ea710839b7e76677\hpvyt13.inf"
[HKEY_USERS\.DEFAULT\Software\Microsoft\TelemetryClient\ThrottleStore\watson\generic\generic\pnpdriverimporterror]
"p1x64p2000003f1p3hpvyt13.infp4a5939bc3a4f5e5423fa649626f8479696da46cd9"="-1"


====== End of Search ======
 
Re: Windows update problem Error Code 0x800703f1

Please go to Device Manager and see if the printer still shows up. If it does, right-click it and uninstall or remove.
 
You must log in or register to reply here.

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

Back
Top