How to fix Windows update error 0x800f0991?
Prefer to fix it yourself? The manual steps follow.
- 7methods
- 5 minutes to 2 hours
- Intermediate
Applies to Windows 11 24H2, 25H2 and 26H2 monthly cumulative updates, for example KB5065426 (OS build 26100.6584) and KB5070773; Windows 10 22H2 in rare cases
7 methods in this guide
Hey, I can't seem to install the latest Windows updates because of the 0x800f0991 error. Are there any tips you could give me to bypass this error code?
Install error 0x800f0991 means Windows Update downloaded a cumulative update but could not install it, because a file the update depends on is missing on the PC. It hit many Windows 11 PCs with KB5065426 (build 26100.6584) and still appears with later updates. Restart, check for updates again, then install the update by hand.
Restart the PC with Start > Power > Restart and select Check for updates again (Fix 1). If the same update keeps failing, download it from the Microsoft Update Catalog and install it with DISM (Fix 2). When that also ends with 0x800f0991, the component store needs repair: run DISM and SFC (Fix 3), then Fix problems using Windows Update (Fix 6), which keeps your apps and files.
| Error | Install error - 0x800f0991 next to a cumulative update. In the servicing logs the code is named PSFX_E_MISSING_PAYLOAD_FILE. |
|---|---|
| Where it appears | Settings > Windows Update, next to the update with a Retry button, and in Update history. The download finishes, the install fails. |
| Main cause | A file or component that the new update builds on is missing from the component store (C:\Windows\WinSxS). Microsoft ties the code to update sequencing or dependency errors. |
| Fastest fix | Restart and retry (Fix 1). If the same KB fails again, install it by hand with DISM (Fix 2). |
| Also written as | 0x800F0991, 800f0991, error 0x800f0991, erreur d'installation - 0x800f0991, errore di installazione - 0x800f0991, erro de instalação - 0x800f0991, installatiefout - 0x800f0991. |
| Affects | Windows 11 24H2 and 25H2 above all. Widely reported with KB5065426 of 9 September 2025 (OS build 26100.6584), later with KB5070773 and other monthly updates. |
| Microsoft's status | No public known issue for this code. Microsoft Learn lists it among servicing errors where an in-place upgrade is the reliable repair (written for Azure servers). |
| Where the cause is written | C:\Windows\Logs\CBS\CBS.log. Search for 0x800f0991, then for Matching binary. |
| Time to fix | 5 minutes for Fix 1, 20 to 40 minutes for Fix 2 and Fix 3, one to two hours for a repair reinstall. |
Facts checked on 15 October 2026. Steps written for Windows 11 (24H2, 25H2 and 26H2).
What install error 0x800f0991 means
0x800f0991 is an error of Component-Based Servicing, the part of Windows that installs updates. It is not a download error and not a network error. The update arrived on the PC, and Windows stopped while it was putting the new system files in place.
Microsoft Learn gives the code the name PSFX_E_MISSING_PAYLOAD_FILE and says it is "associated with update sequencing or dependency errors". Read plainly: the update needs a file (the payload) from an earlier update or from Windows itself, and that file is not where it should be.
| What you see | Where | What it tells you |
|---|---|---|
| Install error - 0x800f0991 | Settings > Windows Update, next to the update, with Retry | The cumulative update downloaded and the installation failed. |
| A failed entry with 0x800f0991 | Settings > Windows Update > Update history | The same failure, kept with its date. The date tells you where to look in CBS.log. |
| PSFX_E_MISSING_PAYLOAD_FILE | CBS.log and the CbsPersist logs | The name of 0x800f0991 inside the servicing log. |
Matching binary (file name) missing for component | CBS.log, a few lines before the error | The exact file and component that the update could not find. |
| Erreur d'installation, errore di installazione, erro de instalação | Windows in another display language | The same error. Only the words in front of the code are translated. |
Microsoft has not published a page for home users about this code. The name and the short description above come from a Microsoft Learn list of servicing errors written for Azure virtual machines. The servicing stack is the same in Windows 11, so the meaning holds, but the Azure tools on that page do not apply to a home PC.
Why Windows update error 0x800f0991 appears
The causes below are ordered from the most likely to the least likely. Each one is tied to the fix that deals with it.
| Cause | How often | How to tell | Fix |
|---|---|---|---|
| One monthly update fails on many PCs at once, as KB5065426 did in September 2025. | Most often | The error started with a new update and news sites report the same code. | Fix 1, Fix 2 |
| A file of an earlier update is missing from the component store, while SFC and DISM report no damage. | Often | CBS.log has a line with Matching binary and a file name. | Fix 2 |
| The component store is damaged. | Sometimes | DISM reports that the store is repairable, or 0x80073712 also appears. | Fix 3, Fix 6 |
| A stuck attempt or a damaged download in the update cache. | Less often | The update fails at once at the same percentage on every retry. | Fix 4, Fix 5 |
| Damage that no repair command reaches. | Rarely | Every fix above ended with 0x800f0991 again. | Fix 6, Fix 7 |
The first row is documented. PCWorld reported on 16 September 2025 that KB5065426 would not install for some users, with 0x800F0991 first in a list that also had 0x800F0922, 0x80071A2D and 0x800F081F. For some of them even the package from the Microsoft Update Catalog failed.

The second row is a report, not a Microsoft statement. In a solved Sysnative thread from October 2025, KB5070773 failed with 0x800f0991 on Windows 11 25H2 although SFC and DISM found no errors. The analyst found the line Matching binary snapshot_support.dll missing for component UserExperience-AIX in CBS.log.
Readers find this page with KB5065426, KB5070773 and KB5121003. The code moves from month to month with whatever update is current, because the missing file is on the PC. A newer update needs the same file and fails the same way until the PC is repaired.
Where CBS.log is and which line explains 0x800f0991
You do not need the log for Fix 1 and Fix 2. Read it when they did not help: the log names the missing file, and that tells you whether a manual install or a repair is your next step.
- Press Win + R, type
%systemroot%\Logs\CBSand press Enter. - Copy
CBS.logto the Desktop and open the copy in Notepad, so the original stays untouched. - Press Ctrl + F and search for
0x800f0991. Note the time of the last hit. - Search for
Matching binaryand for, Errornear that time. - Write down the file name and the component name from that line. They are what support will ask for.

- Microsoft Learn says to check
CBS.logand the olderCbsPersist_*.logandCbsPersist_*.cabfiles in the same folder. A.cabfile opens like a folder in File Explorer. - A
Matching binaryline with a file name points to Fix 2, then Fix 3. - The words
ERROR_SXS_COMPONENT_STORE_CORRUPTormark store corruptpoint to Fix 3, then Fix 6. - No clear line at all: go through the fixes in order.
How to fix Windows update error 0x800f0991
Fix 1 and Fix 2 are aimed at this code and help most readers. Fix 3 to Fix 5 are the general repairs, each in short form with the full procedure linked. Fix 6 and Fix 7 reinstall Windows over itself and keep your apps and files: Microsoft names this as the reliable repair for this family of servicing errors.
| What you see or have | Start with |
|---|---|
| The error appeared with this month's update and the PC has not restarted for days. | Fix 1 |
| The same KB fails every day, and SFC and DISM report no damage. | Fix 2 |
| CBS.log names a missing file, or 0x80073712 also appears. | Fix 3 |
| You do not want to type commands. | Fix 4, then Fix 6 |
| The update fails at once, always at the same percentage. | Fix 5 |
| The manual install also ends with 0x800f0991. | Fix 6, then Fix 7 |
| A work or school PC that gets updates from the organization. | Ask the administrator, with CBS.log |
Fix 1. Restart the PC and check for updates again
5 to 20 minutesNo riskAlways first, and above all when the error appeared with a new monthly update.
A restart finishes servicing work that is waiting on files in use. Cumulative updates also replace each other, so a newer update offered after the restart can install where the old one failed.
- Save your work and select Start > Power > Restart. Use Restart, not Shut down.
- Open Settings > Windows Update and select Check for updates.
- Install everything that is offered. If the failed update is still listed, select Retry next to it.
- If it fails again, restart one more time and repeat the check once.
- Open Settings > Windows Update > Update history and see whether the update is now listed as installed.
Note the KB number of the failed update in Update history now. Fix 2 needs it, and support needs it too.
It worked if: The update installs and asks for a restart, and Update history shows it as successfully installed.
If not: If the same KB fails again with 0x800f0991, install it by hand in Fix 2.
Fix 2. Install the update by hand with DISM from the Microsoft Update Catalog
20 to 40 minutesLow riskOne cumulative update keeps failing, and SFC and DISM report no damage.
The catalog gives the full package instead of the small pieces Windows Update sends, so the files missing on the PC come with it. In the Sysnative case this was the fix: the analyst had the user put the update and KB5043080 in C:\MSU and install it with DISM, and it installed.
- Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
- Find the KB number. Open Settings > Windows Update. A failed or pending update is listed with its KB number; earlier ones are under Update history.
- Check the processor type. Open Settings > System > About and look at System type: an x64-based PC needs the x64 file, an ARM-based PC (for example Snapdragon) needs the arm64 file.
- Search the catalog. Open the Microsoft Update Catalog at catalog.update.microsoft.com in your browser, type the KB number (for example KB5124010) in the search box and press Enter.
- Pick the right row. Find the row whose title names your Windows version and your processor type (x64-based or arm64-based) and select Download on that row.
- Download every file listed. A window lists one or more .msu links. Download all of them into one empty folder, for example C:\packages. On Windows 11 24H2 and later the list can include earlier checkpoint updates that the new one needs.
- Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
- Install several files with DISM. If there are several files, open an elevated Terminal or Command Prompt and run DISM with the newest file. DISM finds the other files in the same folder and installs them in the right order.
DISM /Online /Add-Package /PackagePath:C:\packages\<newest-file>.msu - Restart. Restart the PC when the installation finishes, then run winver again: the OS build should have changed.
These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Install an update from the Microsoft Update Catalog

- Create the folder
C:\MSUand save the downloaded.msufiles there. If the catalog offers more than one file for the update, save all of them. - Right-click Start and select Terminal (Admin). Select Yes when Windows asks for permission.
- Install the update with DISM. Replace the file name with the name of your file:
DISM /Online /Add-Package /PackagePath:C:\MSU\windows11.0-kbXXXXXXX-x64.msu - Wait until DISM says The operation completed successfully. and restart the PC.
- Press Win + R, type
winverand press Enter. The build number should now be the one of the new update.
KB5043080 is the base package that later Windows 11 24H2 and 25H2 updates are built on. Our guide to install error 0x800f0993 explains this chain in detail. Keep only the target update and its base package in the folder.
It worked if: DISM reports The operation completed successfully., and after the restart winver shows the new build number.
If not: PCWorld reported that with KB5065426 even the catalog package failed for some users. If DISM stops with 0x800f0991 too, go to Fix 3.
Fix 3. Repair the component store with DISM and SFC
15 to 40 minutesNo riskCBS.log names a missing file, 0x80073712 also appears, or Fix 2 failed with the same code.
The update failed because a file in the component store is missing. DISM with RestoreHealth downloads clean copies of damaged components, and SFC then repairs the system files built from them.
- Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

Search for cmd and choose Run as administrator. Screenshot: Windows 11 26H2. - Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.
DISM.exe /Online /Cleanup-Image /RestoreHealth
DISM /RestoreHealth running. Screenshot: Windows 11 26H2. - Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.
sfc /scannow
sfc /scannow at 100%. Screenshot: Windows 11 26H2. - Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

The result line tells you what SFC did. Screenshot: Windows 11 26H2.
These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files
A clean result does not rule this error out. In the Sysnative case both tools reported no errors while the missing file still blocked the update. If both are clean, go back to Fix 2 or move on to Fix 6.
It worked if: DISM ends with The operation completed successfully., SFC reports that it repaired files or found no violations, and the update installs after a restart.
If not: Run the troubleshooter in Fix 4 and reset the update cache in Fix 5. They take ten minutes together.
Fix 4. Run the Windows Update troubleshooter
5 minutesNo riskYou do not want to type commands, or the fixes above changed nothing.
The troubleshooter checks the update services and clears a stuck attempt. It cannot put back a missing payload file, but it is free of risk and rules out the simple cases before a reinstall.
- Open Troubleshoot settings. Select Start > Settings > System > Troubleshoot.
- Open the list of troubleshooters. Select Other troubleshooters.

Settings, System, Troubleshoot: select Other troubleshooters. Screenshot: Windows 11 26H2. - Run the Windows Update troubleshooter. Under Most frequent, select Run next to Windows Update. The Get Help app opens and starts the checks.

Windows Update is in the Most frequent group; select Run on its row. Screenshot: Windows 11 26H2. - Read the result. Wait until Get Help finishes. If it found and fixed a problem, it says so and asks whether this solved the problem. Answer the question so it can offer the next step.

Get Help reports what it found and asks if the problem is solved. Screenshot: Windows 11 26H2. - Restart the PC. Restart when the troubleshooter finishes, even if it does not ask you to.
- Check for updates again. Select Start > Settings > Windows Update > Check for updates, and install the updates it finds.
These steps were written for Windows 11 (screenshots: 26H2). The full page with the other versions and what each result means: Run the Windows Update troubleshooter
It worked if: Get Help reports that it found and fixed a problem, and the update installs on the next check.
If not: Clear the update cache in Fix 5.
Fix 5. Reset the Windows Update components and the update cache
10 minutesLow riskThe update fails at once at the same point, and the earlier fixes did not help.
A damaged download in the SoftwareDistribution folder is used again at every retry. Stopping the update services and renaming the folder makes Windows download the update from scratch. It does not repair the component store.
- Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
- Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.
net stop wuauserv net stop bits net stop cryptsvc - Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.
del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" - Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old ren %systemroot%\System32\catroot2 catroot2.old - Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.
net start cryptsvc net start bits net start wuauserv - Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.
These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

It worked if: Windows Update downloads the update again from zero and installs it.
If not: The missing file is inside Windows itself. Use the repair reinstall in Fix 6.
Fix 6. Reinstall Windows over itself with Fix problems using Windows Update
1 to 2 hoursLow riskNothing above worked, or the CBS log shows damage that DISM could not repair.
The reinstall puts a clean copy of your current Windows in place, so the missing payload files are back. Microsoft Learn names an in-place reinstall as the only reliable resolution for this group of servicing errors, including 0x800F0991.
Back up the files you cannot lose before any repair of Windows, even one that keeps them: Back up your files (Windows Backup, File History, Time Machine)
- Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

Fix problems using Windows Update reinstalls the current version and keeps apps, files and settings. Screenshot: Windows 11 26H2. - Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
- Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files
- Keep the PC plugged in and online for the whole reinstall.
- The option is in Settings > System > Recovery. It can be missing on a PC managed by work or school.
- After the reinstall, open Settings > Windows Update and install the update that failed.
It worked if: The PC restarts into the same desktop with your apps and files, and the cumulative update then installs without the error.
If not: If the option is missing or the reinstall fails, run Windows setup yourself in Fix 7.
Fix 7. Run an in-place upgrade with Windows 11 setup and keep your files
1 to 2 hoursLow riskFix 6 is missing or failed, or you want to move to the newest Windows 11 version at the same time.
Setup replaces every system component and keeps your data, apps and settings. PCWorld relayed the Media Creation Tool or the Update Assistant as the workaround that got KB5065426 past 0x800f0991.
- Back up the files you cannot lose, as in Fix 6.
- Open Microsoft's Windows 11 download page and download the Installation Assistant, or the ISO under Download Windows 11 Disk Image (ISO).
- With the ISO: double-click it to open it as a drive and run
setup.exe. With the Installation Assistant: run it and follow it. - When setup asks what to keep, select Keep personal files and apps.
- Leave the PC on and online until it restarts into Windows.
- Open Settings > Windows Update and select Check for updates.
Microsoft Learn describes the same command for servers as setup.exe /auto upgrade /dynamicupdate disable. On a home PC the normal setup window does the same job.
It worked if: Windows starts with your apps and files, winver shows the new build, and the next cumulative update installs.
If not: Read "If the error is still there" below.
If error 0x800f0991 is still there
When the in-place upgrade did not help or could not start, the next step depends on who manages the PC and what CBS.log says.
| Situation | What to do |
|---|---|
| Work or school PC with updates from WSUS, Configuration Manager or Intune | Send the administrator the code, the KB number and a copy of the whole C:\Windows\Logs\CBS folder. |
| Setup itself fails | Free space on drive C: and try again: Free up disk space and delete temporary files. Then use Reset this PC with Keep my files: your apps are removed, your files stay. |
| The PC lost power or froze during an update before the error began | Check the drive for errors before you reinstall: Check a disk for errors (chkdsk) |
| You want an expert to read the log | Post the zipped CBS folder in the Windows Update section of Sysnative Forums or on Microsoft Q&A, with the KB number and the build from winver. |
Forum analysts sometimes send a repair file built from one user's logs. Sysnative marks such a fix with "Do not run this fix on another system." A fix written for another PC can damage yours.
- What to send to support: the exact code, the KB number, the build from winver, the time of the last failed attempt and CBS.log.
- Which fixes you already ran, and the last line DISM printed.
- This is not a hardware fault in itself. The exception is a drive that reports errors in chkdsk: a failing drive damages the store again after every repair.
How to keep error 0x800f0991 from coming back
- Restart when Windows Update asks for it, so pending servicing work is finished before the next update.
- Install the monthly update in the month it arrives, so the PC never has to jump over several updates.
- Keep free space on drive C: before the monthly update. Cumulative updates for Windows 11 are several gigabytes.
- Read CBS.log as soon as the error comes back. The Sysnative user saw the same component fail again a month later.
- Do not delete files in
C:\Windows\WinSxSby hand to save space. Updates build on that folder. - Do not run cleanup scripts that remove packages from the component store.
- Do not switch the PC off while it shows that updates are being installed.
- Do not pause updates for months to avoid the error. The security fixes are in the failed update.
Windows 10 left support on 14 October 2025. A Windows 10 PC that stops installing updates is better moved to Windows 11 with the in-place upgrade in Fix 7, if its hardware allows it.
Frequently asked questions
What does error 0x800f0991 mean?
It means Windows could not install an update because a file the update depends on is missing. Microsoft Learn gives the code the name PSFX_E_MISSING_PAYLOAD_FILE and ties it to update sequencing or dependency errors. The download is fine and the internet connection is not the cause. The fault is in the component store, the folder of system components that every update builds on. CBS.log usually names the missing file a few lines before the error, in a line that starts with Matching binary.
Why does KB5065426 (26100.6584) fail with install error 0x800f0991?
KB5065426 is the Windows 11 24H2 security update of 9 September 2025, OS build 26100.6584. Within a week PCWorld reported that it would not install for some users, with 0x800F0991, 0x800F0922, 0x80071A2D, 0x800F081F and other codes. For some even the package from the Microsoft Update Catalog failed, and the workaround that was reported was the Media Creation Tool or the Update Assistant. Newer updates have replaced KB5065426 since then, so restart and check for updates first, then use Fix 2 or Fix 7.
Why does SFC and DISM find nothing while the update still fails with 0x800f0991?
Because the missing file is not one that SFC checks, and DISM can see the store as healthy when one payload file is gone. In a solved Sysnative case, KB5070773 failed with 0x800f0991 on Windows 11 25H2, and both tools reported no errors. CBS.log showed that snapshot_support.dll was missing for one component. Installing the update with DISM from the downloaded .msu file, with KB5043080 in the same folder, fixed it. That is Fix 2 on this page.
Is 0x800f0991 a known issue that Microsoft will fix?
Not as a published known issue. We found no Microsoft release health entry for this code on 15 October 2026. Microsoft Learn lists 0x800F0991 among servicing errors where an in-place upgrade is the reliable repair, in an article written for Azure virtual machines. For a home PC that means the fault is on the PC, not in one update. Microsoft will not send a fix for it, and the repair is Fix 2, Fix 3 or a reinstall that keeps your files.
Can I update to Windows 11 25H2 when I get 0x800f0991?
Yes, an in-place upgrade is one of the repairs. When the monthly update fails with 0x800f0991, run Windows 11 setup from Microsoft's download page and choose Keep personal files and apps, as in Fix 7. Setup puts a complete copy of Windows in place, so the missing payload file is replaced, and the PC comes out on the newest version. Back up your files first and keep the PC plugged in. After setup, check for updates again.
Do I lose my files with Fix problems using Windows Update or an in-place upgrade?
No. Both reinstall Windows and keep your apps, files and settings, when you choose to keep them. This is different from Reset this PC, which removes your apps even when you keep your files. Still, back up the files you cannot lose before any repair of Windows. A power cut during a reinstall is the main risk, so keep a laptop on its charger. Plan for one to two hours, because Windows downloads a full copy of itself.
Does error 0x800f0991 appear on Windows 10?
It can, because Windows 10 uses the same servicing stack, but the reports we read are almost all about Windows 11 24H2 and 25H2. The fixes are the same: restart, install the update by hand, then DISM and SFC, then an in-place upgrade. Windows 10 left support on 14 October 2025. A Windows 10 PC with this error is a good moment to move to Windows 11 with Fix 7, if the hardware allows it.
Is it safe to skip the update and ignore the error?
Not for long. The update that fails is the monthly cumulative update, which carries the security fixes for Windows. A PC with this error usually fails the next month's update too, because the missing file is still missing. One or two weeks while you work through the fixes is fine. Pausing updates for months to stop the message leaves the PC open to the problems those updates close.
Is this page the same answer for erreur d'installation, errore di installazione or erro de instalação 0x800f0991?
Yes. The code is the same in every language of Windows: only the words in front of it are translated. Erreur d'installation, errore di installazione, erro de instalação, error de instalación and installatiefout all mean install error, and the fixes are the same. The menu names in the steps are the English ones. In another display language, follow the position of the items: Settings, then Windows Update, then the button that checks for updates. The commands are typed the same way on every PC.
Sources
- Microsoft Learn: Troubleshoot Windows Update errors that require in-place upgrades (0x800F0991 = PSFX_E_MISSING_PAYLOAD_FILE, CBS log locations) (learn.microsoft.com)
- PCWorld: Windows 11's September update is borked, won't install for some users (KB5065426, 16 September 2025) (pcworld.com)
- Sysnative Forums: Windows 11 Update Failure, Error 0x800f0991, Cumulative Update KB5070773 (analyst's reading of a user's CBS log) (sysnative.com)
Did this fix work?
One click, no account. It tells the next reader which guides are worth their time.
Questions and experiences: fix Windows update error 0x800f0991
Still broken, or found a fix we did not cover? Ask here: members and our editors answer. Reading is open; writing needs a free account.
…