• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
Locked

‎03-01-2016 09:22 PM

HP Recommended

Hellos! I'm trying to run SFC but I get the notorious Windows Resource Protection could not scan error. I then turned to run DISM but got Error: 605 "The specified buffer contains ill-formed data." Any fixes to this? Thanks!

 

I have an Envy 15t

1 person had the same question
10 REPLIES 10

‎03-02-2016 02:46 AM - edited ‎03-02-2016 02:48 AM

HP Recommended

 

What DISM commands did you enter?

 

Which SFC switches did you use?

 

What event occurred before this error?

 

There must be a particular reason that you decided to run the system repair utilities. Please share that with us.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎03-02-2016 06:52 AM - edited ‎03-02-2016 07:01 AM

HP Recommended

This error never occured before and would rely on Dism to fic my SFC problem. 

 

I used: 

dism /online /cleanup-image /restorehealth

and 

sfc /scannow

 

The SFC Log:

2016-03-02 09:52:32, Info CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:52:32, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2016-03-02 09:52:37, Info CSI 00000070 [SR] Verify complete
2016-03-02 09:52:37, Info CSI 00000071 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:52:37, Info CSI 00000072 [SR] Beginning Verify and Repair transaction
2016-03-02 09:52:42, Info CSI 000000d7 [SR] Verify complete
2016-03-02 09:52:43, Info CSI 000000d8 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:52:43, Info CSI 000000d9 [SR] Beginning Verify and Repair transaction
2016-03-02 09:52:48, Info CSI 0000013e [SR] Verify complete
2016-03-02 09:52:48, Info CSI 0000013f [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:52:48, Info CSI 00000140 [SR] Beginning Verify and Repair transaction
2016-03-02 09:52:53, Info CSI 000001a5 [SR] Verify complete
2016-03-02 09:52:53, Info CSI 000001a6 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:52:53, Info CSI 000001a7 [SR] Beginning Verify and Repair transaction
2016-03-02 09:52:58, Info CSI 0000020c [SR] Verify complete
2016-03-02 09:52:58, Info CSI 0000020d [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:52:58, Info CSI 0000020e [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:03, Info CSI 00000275 [SR] Verify complete
2016-03-02 09:53:03, Info CSI 00000276 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:03, Info CSI 00000277 [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:07, Info CSI 000002dc [SR] Verify complete
2016-03-02 09:53:07, Info CSI 000002dd [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:07, Info CSI 000002de [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:12, Info CSI 00000343 [SR] Verify complete
2016-03-02 09:53:12, Info CSI 00000344 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:12, Info CSI 00000345 [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:17, Info CSI 000003aa [SR] Verify complete
2016-03-02 09:53:17, Info CSI 000003ab [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:17, Info CSI 000003ac [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:22, Info CSI 00000411 [SR] Verify complete
2016-03-02 09:53:22, Info CSI 00000412 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:22, Info CSI 00000413 [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:28, Info CSI 00000478 [SR] Verify complete
2016-03-02 09:53:28, Info CSI 00000479 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:28, Info CSI 0000047a [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:33, Info CSI 000004df [SR] Verify complete
2016-03-02 09:53:33, Info CSI 000004e0 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:33, Info CSI 000004e1 [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:38, Info CSI 00000546 [SR] Verify complete
2016-03-02 09:53:38, Info CSI 00000547 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:38, Info CSI 00000548 [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:43, Info CSI 000005ad [SR] Verify complete
2016-03-02 09:53:43, Info CSI 000005ae [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:43, Info CSI 000005af [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:48, Info CSI 00000614 [SR] Verify complete
2016-03-02 09:53:48, Info CSI 00000615 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:48, Info CSI 00000616 [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:53, Info CSI 0000067b [SR] Verify complete
2016-03-02 09:53:53, Info CSI 0000067c [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:53, Info CSI 0000067d [SR] Beginning Verify and Repair transaction
2016-03-02 09:53:59, Info CSI 000006ea [SR] Verify complete
2016-03-02 09:53:59, Info CSI 000006eb [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:53:59, Info CSI 000006ec [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:04, Info CSI 00000751 [SR] Verify complete
2016-03-02 09:54:04, Info CSI 00000752 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:04, Info CSI 00000753 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:09, Info CSI 000007b8 [SR] Verify complete
2016-03-02 09:54:09, Info CSI 000007b9 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:09, Info CSI 000007ba [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:14, Info CSI 0000081f [SR] Verify complete
2016-03-02 09:54:14, Info CSI 00000820 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:14, Info CSI 00000821 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:19, Info CSI 00000890 [SR] Verify complete
2016-03-02 09:54:19, Info CSI 00000891 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:19, Info CSI 00000892 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:25, Info CSI 000008f7 [SR] Verify complete
2016-03-02 09:54:25, Info CSI 000008f8 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:25, Info CSI 000008f9 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:30, Info CSI 00000967 [SR] Verify complete
2016-03-02 09:54:30, Info CSI 00000968 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:30, Info CSI 00000969 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:37, Info CSI 000009e5 [SR] Verify complete
2016-03-02 09:54:38, Info CSI 000009e6 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:38, Info CSI 000009e7 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:44, Info CSI 00000a51 [SR] Verify complete
2016-03-02 09:54:44, Info CSI 00000a52 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:44, Info CSI 00000a53 [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:49, Info CSI 00000abc [SR] Verify complete
2016-03-02 09:54:49, Info CSI 00000abd [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:49, Info CSI 00000abe [SR] Beginning Verify and Repair transaction
2016-03-02 09:54:55, Info CSI 00000b2f [SR] Verify complete
2016-03-02 09:54:55, Info CSI 00000b30 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:54:55, Info CSI 00000b31 [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:02, Info CSI 00000b98 [SR] Verify complete
2016-03-02 09:55:02, Info CSI 00000b99 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:02, Info CSI 00000b9a [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:08, Info CSI 00000bff [SR] Verify complete
2016-03-02 09:55:08, Info CSI 00000c00 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:08, Info CSI 00000c01 [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:13, Info CSI 00000c66 [SR] Verify complete
2016-03-02 09:55:13, Info CSI 00000c67 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:13, Info CSI 00000c68 [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:19, Info CSI 00000cce [SR] Verify complete
2016-03-02 09:55:19, Info CSI 00000ccf [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:19, Info CSI 00000cd0 [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:26, Info CSI 00000d4f [SR] Verify complete
2016-03-02 09:55:26, Info CSI 00000d50 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:26, Info CSI 00000d51 [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:33, Info CSI 00000dcc [SR] Verify complete
2016-03-02 09:55:33, Info CSI 00000dcd [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:33, Info CSI 00000dce [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:42, Info CSI 00000e6c [SR] Verify complete
2016-03-02 09:55:42, Info CSI 00000e6d [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:42, Info CSI 00000e6e [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:49, Info CSI 00000edc [SR] Verify complete
2016-03-02 09:55:49, Info CSI 00000edd [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:49, Info CSI 00000ede [SR] Beginning Verify and Repair transaction
2016-03-02 09:55:55, Info CSI 00000f49 [SR] Verify complete
2016-03-02 09:55:55, Info CSI 00000f4a [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:55:55, Info CSI 00000f4b [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:01, Info CSI 00000fc5 [SR] Verify complete
2016-03-02 09:56:01, Info CSI 00000fc6 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:01, Info CSI 00000fc7 [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:06, Info CSI 0000103d [SR] Verify complete
2016-03-02 09:56:06, Info CSI 0000103e [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:06, Info CSI 0000103f [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:12, Info CSI 000010ae [SR] Verify complete
2016-03-02 09:56:12, Info CSI 000010af [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:12, Info CSI 000010b0 [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:17, Info CSI 00001116 [SR] Verify complete
2016-03-02 09:56:17, Info CSI 00001117 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:17, Info CSI 00001118 [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:22, Info CSI 00001181 [SR] Verify complete
2016-03-02 09:56:22, Info CSI 00001182 [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:22, Info CSI 00001183 [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:28, Info CSI 000011fd [SR] Verify complete
2016-03-02 09:56:28, Info CSI 000011fe [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:28, Info CSI 000011ff [SR] Beginning Verify and Repair transaction
2016-03-02 09:56:36, Info CSI 00001299 [SR] Verify complete
2016-03-02 09:56:36, Info CSI 0000129a [SR] Verifying 100 (0x0000000000000064) components
2016-03-02 09:56:36, Info CSI 0000129b [SR] Beginning Verify and Repair transaction

I decided to run this just for maintanence sake but cant complete it.

Was this reply helpful? Yes No

‎03-02-2016 07:31 AM

HP Recommended
@systemglytch wrote:

This error never occured before and would rely on Dism to fic my SFC problem. 

 

I used: 

dism /online /cleanup-image /restorehealth  add: /verify /checkhealth /checkintegrity

and 

sfc /scannow  add:  /purgecache /quiet

 I decided to run this just for maintanence sake but cant complete it.

What were the  error messages at the end of the attempt to run sfc and DISM?


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎03-02-2016 08:47 AM

HP Recommended

At first I got:

 

Error: 605 "The specified buffer contains ill-formed data." for DISM

 

and

 

"Windows resource protection could not perform the requested operation" for SFC

 

After I tried the corrected code you sent me (thank you BTW) I got Error 87
"The cleanup-image option is unknown" for DISM

 

And SFC /scannow /purgecache /quiet did not do anything and gave me an index of possible SFC switches instead.

 

Im kind off a noob in this.

Was this reply helpful? Yes No

‎03-14-2016 11:02 AM - edited ‎03-28-2016 02:13 AM

HP Recommended

I suggest that you boot to your recovery media to  access the advanced startup options.

 

What you can do is boot to safe mode and run chkdsk /f at the command line.  

 

 

The following video describes how to make a usb repair flashdrive, which is used to repair your PC when you are having problems.  You can also use the HP recovery media to do this if you have created one.

At minute 1:38 in the following video you will see that there is an option to boot into safe mode.

 


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎03-27-2016 10:56 PM

HP Recommended

Thanks for the reply! I went ahead and tried to run chckdsk /f on safe mode but got " The type of file system is NTFS." 

Was this reply helpful? Yes No

‎03-28-2016 02:16 AM - edited ‎03-28-2016 02:19 AM

HP Recommended

" The type of file system is NTFS."  is not proper syntax. What was the exact error message?

 

Having a disk formatted in FAT32 or NTFS makes no difference to the system file checker. It will run in either file system.

 

Have you made the recovery disk as suggested in the video?

 

You may need to consider using your recovery media flashdrive that you should have created by now to return your operating system to a useful state.

 

For how long have you been unable to use your notebook?

 

Is your notebook still in warranty?

Check your warranty status Here.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎03-28-2016 12:47 PM

HP Recommended

I'm in the process of obtaining a USB to do so. Thanks for the video! My warranty expired. But I'm comfused, would the USB be the same as having the recovery on the drive? I have a recovery partition on the drive. 

Was this reply helpful? Yes No

‎03-28-2016 04:22 PM

HP Recommended

The usb would do the same as the recovery partition's HP Recovery Manager.

 

The usb recovery media flashdrive just happens to be less exposed to corruption and far more durable.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.