sfc /scannow error "could not perform requested operation"

drencrom · May 23, 2020

When I run sfc /scannow in the elevated command prompt I receive the message "could not perform requested operation." If I perform a system restore to my last restore point, sfc /scannow works properly for several days, but then it starts sending me that same error message again. I can then perform another system restore and the process repeats itself. To my knowledge I am not doing anything that would cause the sfc /scannow command to stop working properly. When I look in the CBS.log file I find error codes 0x80004005 and 0x80070002. I'd appreciate any help anyone might be able to give me. Thanks!

zbook · May 23, 2020

Please run these commands while connected to the internet:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan

7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

drencrom · May 24, 2020

Thanks for the help. This is what I came up with.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 99% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 14091

The name of an attribute in an identity is not within the legal range.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 14091

The name of an attribute in an identity is not within the legal range.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 99% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...

726016 file records processed.

File verification completed.

21880 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...

908728 index entries processed.

Index verification completed.

0 unindexed files scanned.

0 unindexed files recovered.

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

91357 data files processed.
CHKDSK is verifying Usn Journal...

40990032 USN bytes processed.

Usn Journal verification completed.

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

1935324159 KB total disk space.
579764876 KB in 578540 files.
381540 KB in 91358 indexes.
0 KB in bad sectors.
894007 KB in use by the system.
65536 KB occupied by the log file.
1354283736 KB available on disk.

4096 bytes in each allocation unit.
483831039 total allocation units on disk.
338570934 allocation units available on disk.

C:\windows\system32>

Sysnative Windows Update · May 24, 2020

Hi!

Please try this:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

Download the portable version of GSmartControl and save it on your Desktop;
Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
Go to the Self-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 or take a screenshot;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
Please note: If the SMART Status reads: Unsupported, stop and let me know.

drencrom · May 25, 2020

Thanks for the help! At this moment, sfc /scannow is still working. Like clockwork, it will undoubtedly stop working withing the next 1-2 days.

zbook · May 25, 2020

drencrom said:
Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 14091

The name of an attribute in an identity is not within the legal range.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 14091

Find a flash drive that you can format (> or = 8 GB)

Create a bootable Windows 8.1 iso:
https://support.microsoft.com/en-us/help/15088/windows-10-create-installation-media
Windows 8.1 Download • Windows ISO
Windows 8.x and Windows 10 Direct Download Links
TechBench by WZT (v4.1.1)

Read about an in place upgrade repair:
Repair Install Windows 8

drencrom · May 26, 2020

Thanks for the advice, but that sounds like more trouble than it's worth. With my luck I'd end up causing more damage than I fixed.

zbook · May 26, 2020

See if you can create the bootable Windows 8.1 iso using the Microsoft link.

Once its available a few commands can be tried to fix the component store error messages.

drencrom · May 30, 2020

Do you think a program like Reimageplus could help me fix this?

zbook · May 30, 2020

Information about the error should be in the log files.

Run new commands using administrative command prompt:
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /checkhealth
4) dism /online /cleanup-image /scanhealth
5) dism /online /cleanup-image /restorehealth
6) sfc /scannow

7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

8) Search for:
a) C:\Windows\Logs\CBS\CBS.log
b) C:\Windows\Logs\Dism\Dism.log

9) Zip files as needed and post share links using one drive, drop box, or google drive.

The prior DISM commands displayed: Error: 14091 = The name of an attribute in an identity is not within the legal range.

The Reimageplus software I've not used.

With a Windows 8.1 iso the problems in the component store may be able to be fixed by running a limitaccess command and using the iso as the source files.

drencrom · May 30, 2020

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 99% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

The component store is repairable.
The operation completed successfully.

C:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 14091

The name of an attribute in an identity is not within the legal range.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 14091

The name of an attribute in an identity is not within the legal range.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 99% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>

Here are the dropbox links for the CBS and DISM logs.

CBS.log

dism.log

zbook · May 31, 2020

See if you can create a bootable Windows 8.1 iso:

Download Windows 8.1 Disc Image (ISO File)

Code:

2020-05-30 10:19:38, Error                 CSI    00000402 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #108997290# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:314{157}]"Microsoft-Windows-Printing-OLEPRN, Culture=neutral, Version=6.3.9600.17415, PublicKeyToken=31bf3856ad364e35, ProcessyToken=31bf3856ad364e35, PronScope=NonSxS")
[gle=0xd0150017]
2020-05-30 10:19:38, Error                 CSI    00000403@2020/5/30:14:19:38.949 (F) base\wcp\componentstore\versionedindex.cpp(1021): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::PopulateComponentFamiliesKey expression: (null)
[gle=0x80004005]

Code:

2020-05-30 10:19:39, Info                  CBS    Failed to get applicability on updates [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_8_for_KB3046737~31bf3856ad364e35~amd64~~6.3.1.0, Update: 3046737-8_neutral_GDR [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Info                  CBS    Failed to evaluate external applicability for package update: 3046737-45_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB3046737_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.0, Update: 3046737-45_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Info                  CBS    Failed to evaluate external applicability for package update: 3046737-75_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB3046737_RTM~31bf3856ad364e35~amd64~~6.3.1.0, Update: 3046737-75_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Info                  CBS    Failed to evaluate external applicability for package update: 3046737-76_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB3046737~31bf3856ad364e35~amd64~~6.3.1.0, Update: 3046737-76_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-05-30 10:19:39, Info                  CBS    Failed to call EvaluateApplicability on internal CBS package. [HRESULT = 0x80073712]

Sysnative Windows Update · May 31, 2020

Please do the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running DISM just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

drencrom · May 31, 2020

Here you go.

Logfile

CBS copy.log

drencrom · May 31, 2020

That link to the logfile in my previous post was wrong. This should be the correct one.

Logfile.7z

Sysnative Windows Update · Jun 1, 2020

Thanks.

Step#1 - 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 the attached fixlist.txt 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.

drencrom · Jun 1, 2020

This is the log file that was generated. But Norton said it stopped the process, so I'm not sure if it is complete.

Fix result of Farbar Recovery Scan Tool (x64) Version: 31-05-2020 01
Ran by Hollis Mulwray (01-06-2020 22:42:45) Run:1
Running from C:\Users\Hollis Mulwray\Desktop
Loaded Profiles: Hollis Mulwray
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing-oleprn_31bf3856ad364e35_6.3.9600.17415_none_6c31d74133001262]
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing-oleprn_31bf3856ad364e35_6.3.9600.17415_none_6c31d74133001262]
"S256H"=hex:1d,86,42,3e,70,9c,98,d8,6e,29,ee,96,e8,6f,c0,8d,ce,0a,71,09,e0,1d,\
86,11,67,8b,bf,27,03,b3,e6,c8
"identity"=hex:4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,50,72,69,\
6e,74,69,6e,67,2d,4f,4c,45,50,52,4e,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,\
74,72,61,6c,2c,20,56,65,72,73,69,6f,6e,3d,36,2e,33,2e,39,36,30,30,2e,31,37,\
34,31,35,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,\
38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,\
68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,\
63,6f,70,65,3d,4e,6f,6e,53,78,53
"c!178948e9734..f3dec0b4b8c_31bf3856ad364e35_6.3.9600.17415_e4e050a5879efaff"=hex:
"f!oleprn.dll"=dword:00000003
"DV"=hex:76,4b,80,25,03,00,06,00
"CTS"=dword:4a955424
"CF"=dword:00000010
EndRegedit:
*****************

========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.

========= End of CMD: =========

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-printing-oleprn_31bf3856ad364e35_6.3.9600.17415_none_6c31d74133001262 => removed successfully
Registry ====> The operation completed successfully.

==== End of Fixlog 22:42:47 ====

Sysnative Windows Update · Jun 1, 2020

Yes, it did complete.

Please retry running DISM with Process Monitor.

drencrom · Jun 2, 2020

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

No component store corruption detected.
The operation completed successfully.

C:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 0x800f0906

The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

C:\windows\system32>

CBS.log

Logfile.7z

drencrom · Jun 3, 2020

I'm not sure if this is related to my current problem or not, but for the last year or so every time I installed a service stack update scf /scannow would stop working and checking for updates would go on endlessly. I ended up having to do a system restore to get rid of the service stack updates. So I haven't downloaded the last few service stack updates.

sfc /scannow error "could not perform requested operation"

Well-known member

Member

Well-known member

Inactive

Well-known member

Member

Well-known member

Member

Well-known member

Member

Well-known member

Member

Inactive

Well-known member

Well-known member

Inactive

Attachments

Well-known member

Inactive

Well-known member

Well-known member