In anticipation of the release of Windows 8 on sale, Microsoft released a large cumulative update KB2756872, which has never been done before for client operating systems. However, when installing the update, an unpleasant surprise awaited me - error 80073712.

Today I'll show you how to overcome this and a number of other errors when installing Windows updates using the new servicing feature - in-box corruption repair.

This entry opens a series of articles about what's new in Windows maintenance. And no, it has nothing to do with automatic maintenance via the scheduler. First, I will show how I solved the problem with installing the update, and then I will talk about the technology.

Today on the program

Troubleshooting Windows Update Errors Caused by Component Store Corruption

In the help of previous Microsoft OS for the error 80073712 there is a description that suggests that the cause is component store corruption. For Windows Vista and Windows 7, the System Update Readiness Tool (CheckSUR) was released to fix a number of Windows Update errors.

80070002 ERROR_FILE_NOT_FOUND 8007000D ERROR_INVALID_DATA 800F081F CBS_E_SOURCE_MISSING 80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT 800736CC ERROR_SXS_FILE_HASH_MISMATCH 800705B 9 ERROR_XML_PARSE_ERROR 80070246 ERROR_ILLEGAL_CHARACTER 8007370D ERROR_SXS_IDENTITY_PARSE_ERROR 8007370B ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME 8007370A ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_ VALUE 80070057 ERROR_INVALID_PARAMETER 800B0100 TRUST_E_NOSIGNATURE 80092003 CRYPT_E_FILE_ERROR 800B0101 CERT_E_EXPIRED 8007371B ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE 80070490 ERROR_N OT_FOUND

To fix these errors in Windows 8 and newer operating systems, the CheckSUR utility is not needed, because everything you need is already built into the system! You can repair corrupted components using the PowerShell cmdlet (recommended method) or the DISM.exe utility.

Upd. 28-Jul-2015. Microsoft has released a special update that brings native component recovery to Windows 7, similar to Windows 8+.

Stage 1 - Recovering a Corrupted Component Store

Recovery can be performed without a Windows installation disc, but in some cases you may need it.

Recovery without an installation disc

In this case, the storage files on the local drive and Windows Update are used.

The state of the component store is indicated by the parameter Image Health State. Him Healthy means that everything is fine with the component store. For further diagnostics, go to checking the integrity of system files just below ↓ If the storage corruption is not fixed, you need to try to do it using the installation disk.

Recovery using the installation disc

When the system fails to repair any components, the original installation disc can help you.

  1. Right click on the ISO image and select from the menu To plug. Pay attention to the drive letter that the mounted image got.
  2. In PowerShell, run the command: Repair-WindowsImage -Online -RestoreHealth -Source:WIM:E:\sources\install.wim:1

    Here, "E" corresponds to the letter of the mounted image, and "1" corresponds to the edition index in the image (the example uses a Windows 8 Enterprise image with a single edition).

  3. At the end of the procedure, make sure that the component store is in order (Healthy).

Stage 2 - checking the integrity of system files

Strictly speaking, this step has nothing to do with restoring components. However, Microsoft technical support recommends that after checking the integrity of the component store, you also check the integrity of system files. To do this, at the command prompt, run as administrator, run the command:

Sfc /scannow

One of my files got corrupted and SFC repaired it successfully.

Cases where the system failed to recover any files are beyond the scope of this article (I'll cover them another time).

Stage 3 - Installing the update

So, two commands restored the integrity of the component store and system files. It's time to try installing the update again.

As you can see, this time everything worked for me!

What is Windows maintenance and why is it needed

Benefits of Built-in Windows Component Recovery

Let's compare the key points of component recovery in different operating systems.

Windows Vista and Windows 7

Purpose of verification (working system and images)

The target of the scan can be either an installed system or an image in WIM or VHD format.

Checks a running system.

Checks the mounted offline image at the path specified after the parameter.

Checking and restoring storage

The Repair-WindowsImage cmdlet provides three parameters that perform storage validation to determine the status and restore components. The result of the scan may be:

  • no damage (Healthy)
  • the presence of damage that can be repaired (Repairable)
  • the presence of damage that cannot be repaired (Not repairable)

However, the parameter functions are different.

-CheckHealth

Instantly checks if a corruption marker is present in the system registry. This token may appear during the operation of the maintenance system.

-ScanHealth

Checks storage for damage. This operation takes more time than a simple token check.

-RestoreHealth

Checks the vault for corruption and repairs it. This operation is the longest of the three.

Source of recovery components

To restore components, they need to be taken from somewhere. When the source not specified, the check automatically uses the local component store and Windows Update.

This point is not documented anywhere, and you should understand that when checking an offline Windows image from a different edition or version of Windows, the source must be specified.

In both cases, you can specify more than one source and even block Windows Update from doing so. The options below are for recovery only and therefore only valid in conjunction with -RestoreHealth.

As a source, you can use the path to:

  • a running system that can be accessed over the network
  • standalone image, and its preliminary connection is optional

Here, it is interesting to be able to specify the path directly to the publication in the WIM image without first copying it to a local disk and then connecting it. It is secret knowledge, not yet documented ;) This works thanks to the WIM auto-mount feature implemented in the last stages of development of Windows 8.

You can list multiple paths separated by commas. Additional sources are used only if there were no suitable components in the previous ones.

When a WIM image is used as the source, you must specify the image type and its index:

Source:WIM:E:\sources\install.wim:1

-Limit Access

Blocks access to Windows Update during the scan.

PowerShell command examples

I will give some examples of practical use of the Repair-WindowsImage cmdlet with different targets and sources of verification. You already saw the first two at the beginning of the article.

Restoring a live system storage using local files and Windows Update as a source:

Repair-WindowsImage -Online -RestoreHealth

Restoring a live system storage using Windows Update and a WIM image as sources:

Repair-WindowsImage -Online -RestoreHealth -Source:WIM:E:\sources\install.wim:1

Checking the offline VHD image storage. It first mounts to the C:\mount folder (this is very fast), and then it checks.

Mount-Windowsimage -ImagePath C:\vhd\Win8.vhd -Index 1 -Path C:\mount Repair-WindowsImage -Path C:\mount -ScanHealth

Restoring an offline VHD image storage using a WIM image as a source. First, the VHD is mounted to a folder, then the image is restored, after which the VHD is disconnected and the changes are saved.

Mount-Windowsimage -ImagePath C:\vhd\Win8.vhd -Index 1 -Path C:\mount Repair-WindowsImage -Path C:\mount -RestoreHealth -Source:WIM:E:\sources\install.wim:1 Dismount- WindowsImage -path C:\mount -Save

Results of verification and recovery

In addition to the results in the console, you can find a detailed report near the end of the %WinDir%\Logs\DISM\dism.log file

The first half of the above snippet shows specific components and the result of their recovery (success or failure), and the second half shows a summary of the operation, including the time it took to complete.

Checking System Update Readiness. (p) CSI Manifest Corrupt (Fixed) amd64_microsoft-windows-lpksetup_31bf3856ad364e35_6.2.9200.16384_none_7a23086df63cad13 (p) CSI Manifest Corrupt (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3 856ad364e35_6.2.9200.16384_en-us_2422e0b40b0ac235 (p) CSI Manifest Corrupt ( (p) CSI Manifest Corrupt (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364 e35_6.2.9200.16384_en-us_53ea2a36610cb913 (p) CSI Manifest Corrupt ( (p) CSI Manifest Corrupt (Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e 35_6.2.9200.16384_en-us_8e2bd9e9b9aeac5f (p) CSI Manifest Corrupt ( Fixed) amd64_microsoft-windows-l..oyment-languagepack_31bf3856ad364e35_6.2.9200.16384_c73545896a8993dd Summary: Operation: Detect and Repair Operation result: 0x0 Last Successful Step: Entire operation completes. Total Detected Corruption: 7 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 7 CSI Metadata Corruption: 0 CSI Payload Corruption: 0 Total Repaired Corruption: 7 CBS Manifest Repaired: 0 CSI Manifest Repaired: 7 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True Total Operation Time: 221 seconds.

As you can see, I had 7 manifests related to the language pack damaged, which became an obstacle to installing the Windows update. All damage has been repaired.

Of course, this material does not imply immediate practical application, although you can check the status of the Windows component store right now. Moreover, in three years of working in Windows 7, I have never had problems installing updates.

However, Windows Update errors related to storage corruption are not at all uncommon, even if only to judge by the OSZone forum. Therefore, it is important to know how to deal with them.

It seemed to me that part of the blog audience was frankly bored with a series of articles about the modern Windows 8 interface and applications. Of course, everything is primitive there, there are no technical subtleties, and most importantly, some people get the feeling that there is nothing new in Windows 8 besides Modern UI. This is wrong…

I had been planning a series of posts about changes in Windows maintenance for a long time, and the problem with installing the update only forced the publication, at the same time forcing me to change the order of the articles in the series.

Did you have enough technical subtleties today? ;)

If not, the next post in this series will not only take you on a journey into the history of Microsoft's OS maintenance tools, but also a unique opportunity to try your hand at being a Windows r-collector! But before that, blog entries on other topics will appear.

Returning to the Component Store technology in Windows 8, let's look at recovery scenarios. Recall that starting with Windows Vista, Microsoft introduced the concept of component based servicing. Thanks to the component structure, it was possible to create a more stable system for installing / removing updates, patches and SP service packs. The same system underlies the architecture of Windows 8. Windows Component Store files on disk are located in the directory \ Windows\ WinSxS, which tends to grow significantly over time in size (read more about why the size of this directory grows over time and how to reduce the size of the WinSxS folder).

However, in some cases, the component store can become corrupted, which leads to problems when installing Windows updates and other Microsoft software. To restore the component store in previous versions of Windows (Windows Vista, Windows 7, Windows Server 2008 / R2), Microsoft has developed a special utility - CheckSUR or System Update Readiness Tool (KB947821). This utility is quite large in size (more than 350 MB), and as new Windows updates are released, it is regularly updated. This means that every time you have to download a fresh version CheckSUR.

Advice. In one of the previous articles, we already considered an example of using CheckSUR to find and restore damaged components: .

What does this utility do? The System Update Readiness Tool checks the integrity of the following resources:

    Files in directories:
  • %SYSTEMROOT%\Servicing\Packages
  • %SYSTEMROOT%\WinSxS\Manifests
    The contents of the registry branches:
  • %SYSTEMROOT%\WinSxS\Manifests
  • HKEY_LOCAL_MACHINE\Schema
  • HKEY_LOCAL_MACHINE\Components
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing

In the event that CheckSUR finds errors or inconsistencies, it will attempt to repair them.

Component store issues can cause various errors when installing Windows updates. Below is a list of typical error codes that this utility should fix.

List of WindowsUpdate errors caused by component store corruption

Code error Description
0×80070002ERROR_FILE_NOT_FOUNDThe system cannot find the file specified.
0x8007000DERROR_INVALID_DATAThe data is invalid.
0x800F081FCBS_E_SOURCE_MISSINGThe source for the package or file not found.
0×80073712ERROR_SXS_COMPONENT_STORE_CORRUPTThe component store is in an inconsistent state.
0x800736CCERROR_SXS_FILE_HASH_MISMATCHA component's file does not match the verification information present in the component manifest.
0x800705B9ERROR_XML_PARSE_ERRORUnable to parse the requested XML data.
0×80070246ERROR_ILLEGAL_CHARACTERAn invalid character was encountered.
0x8007370DERROR_SXS_IDENTITY_PARSE_ERRORAn identity string is malformed.
0x8007370BERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAMEThe name of an attribute in an identity is not within the valid range.
0x8007370AERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUEThe value of an attribute in an identity is not within the valid range.
0×80070057ERROR_INVALID_PARAMETERThe parameter is incorrect.
0x800B0100TRUST_E_NOSIGNATURENo signature was present in the subject.
0×80092003CRYPT_E_FILE_ERRORAn error occurred while Windows Update reads or writes to a file.
0x800B0101CERT_E_EXPIREDA required certificate is not within its validity period when verifying against the current system clock or the time stamp in the signed file.
0x8007371BERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETEOne or more required members of the transaction are not present.
0×80070490ERROR_NOT_FOUNDWindows could not search for new updates.

In Windows 8 and Windows Server 2012, functionality similar to the CheckSUR utility is already built into the system and is called inboxCorruptionRepair(built-in component recovery). Built-in component recovery can work in two modes: background And manual. Background Repair automatically starts if errors occur when you try to install a Windows Update. Windows in this case automatically tries to fix the damaged component and reinstall the Windows Update package. In the event that automatic repair cannot fix the problem on its own, the administrator can fix the errors manually by restoring the component store to a healthy state. You can do this using the DISM Image Servicing Utility (command Dism /Online /Cleanup-Image) or using Powershell (cmdlet Repair-WindowsImage).

To check the status of the component store, open an elevated command prompt and run:

Dism /Online /Cleanup-Image /CheckHealth

Adviсe.

  1. DISM, unlike most Windows utilities, is case sensitive.
  2. The Dism /Cleanup-Image command saves logs to C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\DISM\dism.log

Similar Powershell command:

Repair-WindowsImage -Online -CheckHealth

The CheckHealth check will take a few minutes. As you can see, the current status of the component store in the image is Healthy. recovery is not required.

In the event that any problems or errors are found, you should start the storage recovery procedure with the command:

Dism.exe /Online /Cleanup-Image /Restorehealth

Similar Powershell command:

Repair-WindowsImage -Online -RestoreHealth

In this example, system file recovery was successful:

The restore operation completed successfully. The component store corruption was repaired.

In the event that the system was unable to restore some components in the storage on its own, you may need the distribution kit (installation disk) of Windows 8. Insert this disk into the drive or. Let's say the drive with the distribution is assigned the letter E. Let's get a list of available versions of Windows 8 on the drive using the PoSH command:

Get-WindowsImage -ImagePath E:\sources\install.wim

In this example, we see that there is only one image on the disk (Windows 8 Pro) with index 1 (Index: 1).

The following command will start a vault repair, restoring the damaged components from the original Windows 8 image:

Repair-WindowsImage -Online -RestoreHealth -Source G:\sources\install.wim:1

After the restoration is completed, make sure that the component store is in a healthy state (status: Healthy)

The next (not always mandatory) step is to check the integrity of system files using the command:

Sfc /scannow

Advice. If you resorted to repairing the Component Store because of problems installing Windows updates, restart the Windows Update service and reset the local update cache. To do this, run the following commands on the command line:

Net stop wuauserv net stop bits net stop cryptsvc ren %systemroot%\SoftwareDistribution oldSD ren %systemroot%\System32\catroot2 oldCat2 net start cryptsvc net start bits net start wuauserv

I haven't written anything for a long time exclusively to Windows 7. The reason for today's entry was the rarest case - Microsoft added a new feature to the old OS retroactively!

Experienced readers will immediately remember how, four years after the release of Windows 7, it became possible to clean up the WinSXS folder. Then some of the DISM functions were transferred from Windows 8+. Two years have passed, and another technology associated with the component store has moved to Windows 7.

Today on the program

Back to printed

From it you will learn:

  • basics of the Windows servicing system
  • steps to restore components in Windows 8+
  • the difference between the old CheckSUR in Windows 7 and built-in recovery in Windows 8+

What's new in Windows 7 :)

Microsoft has published knowledge base article KB2966583 from which you can download the update package. After installing it and rebooting, Windows 7 gets virtually the same ability to restore components as Windows 8+.

As with newer OSes, recovery is implemented using DISM. The following command starts the process of checking the repository and repairing damaged components.

DISM /Online /Cleanup-Image /ScanHealth

However, Windows 7 has a number of features:

  • there are no keys here /CheckHealth And /RestoreHealth, and the key does all the work /ScanHealth
  • the command can only be executed on a running system, i.e. recovery of disabled images is not implemented
  • there was an opportunity to check and restore Internet Explorer components, which was not in the old CheckSUR

The result of the command should be viewed in the log, as before, saved at \Windows\logs\CBS\checksur.log

================================ Checking System Update Readiness. Binary Version 6.1.7601.18489 2015-07-27 12:32 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store Summary: Seconds executed: 149 No errors detected

I did not find any damage on the VM, but you can check it for yourself.

The KB article specifically mentions the ability to create a scheduled task to run a command. However, please note that you need administrator rights to run DISM, i.e. the task will not work under a regular account.

Discussion and Poll

If you have questions or comments on the topic of component recovery, feel free to voice them in the discussion. Please don't post the checksur log in the comment text - there is PasteBin .

However, I think that there will be few of them, so I want to turn the discussion into a different plane. There are only a couple of days left before the official release of Windows 10. There are no surprises for insiders and enthusiasts - we have been following the development of the OS for eight months. It is clear that almost all owners of Windows 8.1 will upgrade to Windows 10.

So I'm especially interested in how many people are willing to upgrade to Windows 10 from Windows 7 and earlier.

I already did a Windows 10 upgrade speed survey, but there was no breakdown for your current system, and now we will see it. If Windows 10 IP is your primary current system, please list the one that came before it.

Write in the comments why you will or will not switch to Windows 10! Don't forget to include how long and how you've been using Windows 10 preview.

When working on the Windows 10 operating system, and any other, anything can happen. For example, while working, you notice terrible brakes. There is an idea that a virus or viruses have worked. When checking with an antivirus, there is a chance to find viruses, and when you clean them, it’s not a fact that there will be any changes, since they managed to screw up.

So, to check Windows files for integrity, you can run the utility sfc /scannow from the command line and if a message appears that "Windows Resource Protection found corrupted files but couldn't repair some of them" then this article will help you get rid of this error. If you have Internet access, you can use the article:.

When you scan the system for the integrity of components, if damaged files are found, they are replaced with working ones from . Maybe this folder has been deleted or the files in it are damaged, then you will see a message that "Resource Protection found corrupted files...".

How to Repair a Damaged Component Store Using Power Shell

Read where I repaired the component store using the following command:

DISM /Online /Cleanup-Image /RestoreHealth

For it to work, you need to be connected to the network, as the command contacts the update center and downloads the necessary files from there. It is possible that this command will not help either, then we will use a more powerful tool -.

Click on the search icon on the taskbar, and then enter the phrase "PowerShell", choose the item from the results Windows PowerShell, right-click on it and click on the option "Run as administrator".

In the window that opens, enter the following command:

Repair-WindowsImage -Online -RestoreHealth


For everything to work, you also need the Internet. You need to wait a little while the files are downloaded, after which the component store will have a healthy state and the system will not bring you errors.

If everything went well, then in the results you should notice the line:

ImageHealth State: Healthy


It means that everything is restored.

What to do if there is no Internet to restore the component store?

In this case, you will need a boot disk, or a USB flash drive with Windows 10. Almost any image will do, it is desirable that there be a dozen. Can be downloaded from the Microsoft website.

After downloading the image, double-click on it, thus creating a virtual drive. See what letter he has in the explorer, for example, it can be F.

We return to PowerShell again and enter the following command:

Dism /Get-WimInfo /WimFile:R:\sources\install.wim , Where R: drive letter created by the image, with Windows 10 installation files. This command will determine what kind of system image is in the virtual drive.
Repair-WindowsImage -Online -RestoreHealth -Source R:\sources\install.wim:1

Letter R is our drive, and the figure 1 – index of the image from the first command.

After restoring, try running the system file integrity check again - sfc /scannow, most likely you will see a message that everything damaged was successfully restored.

Is it possible to restore a completely destroyed/deleted storage, WITHOUT reinstallation the whole system?

The client's entire system disk was clogged and WinSxS seemed to be taking up a lot of space, and was removed.
Actually, in a freshly installed Win10, removing 5.5 GB of WinSxS frees only ~380 MB. Everything else is hard links.
What then is stored there?і

I wanted to restore by installing from the install.wim image, and choosing " Refresh with save files", but then a proposal to restart the computer and continue the restorer. And what to continue - no return points and system images were created.
That. There is NO way to restore by installing from disk?

Then I replaced all WinSxS from boot.wim and Win10 started to start normally. It became interesting, and I checked: everything starts in 32bit Win10, but 32bit applications do not start in a 64bit Win10 system.

But you still need to restore the repository completely. Then I came across your site.

By the way, in the Win10 that I am restoring, there is no powershell at all either in the Search, or in the Start_Menu, or in the Control Panel, although there is a \Program Files\WindowsPowerShell directory, but nothing could be launched there. I thought to find and install powershel, l but after spending 30 minutes I found only manuals, on which I stopped wasting time.

Then just in Adnin.cmd window pasted powershell and got it. You missed this easy way to open powershell

So far, I have tried to restore the storage completely without success, and in a working system with a truncated WinSxS:
------
>
>
DISM system
Version: 10.0.10240.16384
Image version: 10.0.10240.16384
[==========================100.0%==========================]
Error: 0x800f081f
Could not find source files.
Specify the location of the files needed to restore the component using the Source option.
------

And in powershell
>

string:1 character:1
+ Repair-WindowsImage -Online -RestoreHealth
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---------------
and from other running systems:

>

Repair-WindowsImage: The system cannot find the specified path.
string:1 character:1
+ Repair-WindowsImage -Path e: -RestoreHealth -Source R:\sources\instal ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo: NotSpecified: (:) , COMException
+ FullyQualifiedErrorId: Microsoft.Dism.Commands.RepairWindowsImageCommand

with the same success. Maybe I'm doing it wrong?

I read above about the same failures, and I also want to get to the bottom of the truth. To do this, I installed Win10 in a 12GB vhd image - I'll screw up one copy, I take on another.
By the way, can you advise how and how to compare the speed of the system with a vhd image and from a disk.

I deal only with pirates, but everything described worked fine on other Win10. Even for example, from ru_windows_10_enterprise_2015_ltsb_x64 to Win10ProRU downloaded yesterday from the update center and back. Incl. the problem is not in the pirates, but somewhere in the broken identification files.

And how is it correct in this case: "use the ISO image of Windows"?

P.S. After copying the entire WinSxS into the destroyed Win10 from the 64bit Win10 image installed in vhd from yesterday, everything starts and works.
But the above checks do NOT work.

I also read your useful articles, but so far I have not been able to completely fix the system with the "touched" WinSxS. It looks like something has changed in the settings.

From a running or other OS:
>sfc /scannow
>sfc /scannow /offbootdir=C:\w10\ /offwindir=E:\Windows
Windows Resource Protection cannot start the recovery service.

>Dism /Online /Cleanup-Image /RestoreHealth
>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:R:\sources\install.wim:1 /limitaccess
>Repair-WindowsImage -Online -RestoreHealth
>Repair-WindowsImage -Path e: -RestoreHealth -Source R:\sources\install.wim -Debug -Verbose
>Repair-WindowsImage -Path e: -RestoreHealth -Source C:\w10\ -Debug -Verbose
VERBOSE: Version 10.0.0.0 of the DISM PowerShell cmdlets
Repair-WindowsImage: The system cannot find the specified path.
string:1 character:1
+ Repair-WindowsImage -Path e: -RestoreHealth -Source C:\w10\ -Debug -V ...

I don't see any other combinations.

So is it possible to recover a destroyed/deleted storage either by restoring from the installation disk, or by commands?

And you may also know - for the *.vhd image, diskmgmt without a choice creates Block_size 2MB, sector 512, and BOOTICE.exe for *.vhd Block_size 2MB, sector 512 (or 4096), and for *.vhdx it offers Block_size 32MB, sector 512 (or 4096).
It's clear with the sector - 1/2 of the sector size is lost on each file, but fewer (large) sectors are easier to process.
But how does it affect and what is the optimal Block_size for images under Windows-10 with a size of 10-25 GB?

Thanks in advance for any information.

P.S.S. When I first sent, my network cable pulled out and the sending hung. I inserted the cable, looked - there was no my post, Then I repeated it. And now I add, and I see 2 posts. Please remove the first one.

After adding full WinSxS, powershell appeared in Search