{"id":5957,"date":"2017-11-22T10:01:33","date_gmt":"2017-11-22T10:01:33","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=5957"},"modified":"2024-04-07T15:31:50","modified_gmt":"2024-04-07T10:01:50","slug":"fix-dism-error-50-minint-windows-pe-servicing","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/fix-dism-error-50-minint-windows-pe-servicing\/","title":{"rendered":"DISM Error 50 or Error 87 “DISM does not support servicing Windows PE”"},"content":{"rendered":"

When you run the DISM tool (with the \/online<\/code> switch) to scan or restore the health of the operating system components, the tool may throw up Error 50<\/code>. Here is the full error message verbatim:<\/p>\n

Deployment Image Servicing and Management tool\nVersion: 10.0.19041.844\nError: 50\n\nDISM does not support servicing Windows PE with the \/Online option.\n\nThe DISM log file can be found at C:\\Windows\\Logs\\DISM\\dism.log\n<\/pre>\n
\"dism<\/p>\n
On Windows 11, you may see a different error code — Error 87.<\/p>\n
Deployment Image Servicing and Management tool\nVersion: 10.0.22621.1\n\nImage Version: 10.0.22621.1992\n\nError: 87\n\nThe cleanup-image option is unknown.\nFor more information, refer to the help by running DISM.exe \/?.\n<\/pre>\n
\"dism<\/p>\n
This occurs when running any of these \/online<\/code> commands to scan or repair the components<\/a> of the running Windows 8\/10\/11 installation:<\/p>\n
Dism \/Online \/Cleanup-Image \/CheckHealth\nDism \/Online \/Cleanup-Image \/ScanHealth\nDism \/Online \/Cleanup-Image \/RestoreHealth<\/pre>\n
Related article: Repair Windows 10\/11 Using DISM and SFC<\/a><\/em><\/p>\n
The DISM.log file may contain the following errors and warnings:<\/p>\n
\nError      DISM   DISM SetupPlatform Provider: PID=6748 TID=4916 SetupPlatformProvider is not supported when running DISM online in Windows PE - CSetupPlatformManager::Initialize(hr:0x80070032)\nWarning    DISM   DISM Provider Store: PID=6748 TID=4916 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070032)\nWarning    DISM   DISM Provider Store: PID=6748 TID=4916 Failed to load the provider: C:\\Windows\\System32\\Dism\\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070032)\nError      DISM   DISM.EXE: No providers were found that support the command(cleanup-image). HRESULT=80070057\n<\/pre>\n
ReAgentC.exe errors<\/strong><\/p>\n
When you run the “reagentc \/info” command, it may show the following output:<\/p>\n
REAGENTC.EXE: A target Windows installation must be specified.<\/pre>\n
When you run “reagentc \/enable”, the following output may be shown:<\/p>\n
\nEnables the local copy of the Windows Recovery Environment (Windows RE).\n\nThis command can be used from the running operating system without additional\nparameters, or from the Windows Preinstallation Environment (Windows PE) using\nthe optional \/osguid parameter.\n<\/pre>\n
The system thinks you’re running WinPE even though you booted into Windows 10\/11.<\/p>\n
Cause<\/h2>\n
DISM and REAGENTC.exe think you’re running Windows PE<\/h4>\n
Apparently, the DISM and the ReAgentC.exe tools think that you’re using them from the Windows Preinstallation Environment (Windows PE) or Windows Recovery Environment (Windows RE), whereas you may be running the tool on a running<\/strong> operating system.\u00a0The presence of the following registry key causes Windows to think that you’re running Windows PE.<\/p>\n
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\MiniNT<\/pre>\n
Windows PE is a standalone preinstallation environment and is an integral component of other setup and recovery technologies, such as Setup for Windows, Windows Deployment Services (Windows DS), the Windows Recovery Environment<\/a> (Windows RE), etc.<\/em><\/p>\n
\n
The “MiniNT” key doesn’t exist by default when you install Windows. As for how the key ended up on your registry, it’s possible that you (or a third-party program) have applied the following registry tweak in an attempt to enable ReFS file system format.<\/p>\n
[HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\MiniNT]\n\"AllowRefsFormatOverNonmirrorVolume\"=dword:00000001<\/pre>\n
Resilient File System (ReFS) is a Microsoft proprietary file system with the intent of becoming the “next generation” file system after NTFS. You can read more on that in Microsoft Docs post Resilient File System (ReFS) overview<\/a>.<\/p>\n
Or it may have the following entries:<\/p>\n
\n\"DoNotCreatePagefile\"=dword:00000001\n\"MaxPageFileUsage\"=dword:00000000\n\"CrashDumpEnabled\"=dword:00000000\n\"AutoReboot\"=dword:00000000\n\"KernelDumpOnly\"=dword:00000000\n\"WriteDebugInfo\"=dword:00000000\n<\/pre>\n<\/div>\n
Please note that the MiniNT key and those registry values don’t exist in a standard Windows installation.<\/p>\n
Resolution<\/h2>\n
To fix DISM Error: 50 “DISM does not support servicing Windows PE” and Error: 87 “The cleanup-image option is unknown”, delete the MiniNT<\/code> registry key using these steps:<\/p>\n
    \n
  1. Right-click Start, click Run.<\/li>\n
  2. Type regedit.exe<\/code> and click OK.<\/li>\n
  3. Navigate to the following registry key:\n
    HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\MiniNT<\/pre>\n
    \"dism<\/li>\n
  4. Right-click MiniNT<\/code>, and choose Delete<\/li>\n
  5. Exit the Registry Editor.<\/li>\n
  6. No restart is required, usually. See if you can\u00a0run DISM<\/a> now.<\/li>\n<\/ol>\n
    \n
    Can’t delete the MiniNT key?<\/h4>\n
    In some cases, you’re unable to delete the MiniNT<\/strong> registry value. You receive the following error when doing so:<\/p>\n
    Cannot delete MiniNT. Error while deleting key.<\/pre>\n
    Also, when right clicking on the “MiniNT” key, the delete option in the  context menu grayed out.<\/p>\n
    This is because the BCD may have an incorrect entry.<\/p>\n
    The “winpe<\/strong>” entry in the BCD is the culprit. Here is what the output may look like when you run the command BCDEDIT on the subject computer:<\/p>\n
    \nWindows Boot Loader\n-------------------\nidentifier              {current}\ndevice                  partition=C:\npath                    \\Windows\\system32\\winload.efi\ndescription             Windows PreInstallation Environment<\/strong>\nlocale                  en-us\ninherit                 {bootloadersettings}\nisolatedcontext         Yes\nallowedinmemorysettings 0x15000075\nosdevice                partition=C:\nsystemroot              \\Windows\nnx                      OptOut\nwinpe                   Yes<\/strong>\n<\/pre>\n
    In this case, you need to fix the Boot Configuration Database (BCD).<\/p>\n
    Please run these two commands from admin Command Prompt:<\/p>\n
    bcdedit \/export c:\\bcd.bak\n\nbcdedit \/deletevalue {current} winpe<\/pre>\n
    Reboot Windows.\n<\/p><\/div>\n
    This fixes the DISM Errors 50 and 87 on Windows 10 and 11, respectively.<\/p>\n
    Note that the DISM error 87 has multiple causes and the “MiniNT” key is just one<\/strong> of those causes. The DISM log<\/a> needs to be analyzed to find the reason for the DISM error code 87.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
    When you run the DISM tool (with the \/online switch) to scan or restore the health of the operating system components, the tool may throw up Error 50. Here is the full error message verbatim:<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[8,869,10],"tags":[160,191,441],"class_list":["post-5957","post","type-post","status-publish","format-standard","hentry","category-windows-10","category-windows-11","category-windows-8","tag-dism","tag-error-messages","tag-registry"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":29438,"url":"https:\/\/www.winhelponline.com\/blog\/dism-error-2-start-servicing-process\/","url_meta":{"origin":5957,"position":0},"title":"DISM Error 2 While Attempting to Start the Servicing Process","author":"Ramesh","date":"October 23, 2022","format":false,"excerpt":"When you run the DISM utility in Windows to clean up the component store or repair Windows system files, error 2 (0x80070002 - ERROR_FILE_NOT_FOUND) may appear: Deployment Image Servicing and Management tool Version: 10.0.22621.1 Error: 2 An error occurred while attempting to start the servicing process for the image located\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"80070002 dism error 2","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/10\/dism-error-2.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/10\/dism-error-2.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/10\/dism-error-2.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":80286,"url":"https:\/\/www.winhelponline.com\/blog\/dism-error-1726-component-store-cleanup\/","url_meta":{"origin":5957,"position":1},"title":"DISM Error 1726 during Component Store Cleanup","author":"Ramesh","date":"February 20, 2026","format":false,"excerpt":"When you attempt to clean up the component store using the following DISM command on a Windows 11 24H2 or 25H2 system, the error code 1726 may occur. DISM \/Online \/Cleanup-Image \/StartComponentCleanup Deployment Image Servicing and Management tool Version: 10.0.26100.5074 Image Version: 10.0.26200.7462 [== 5.8% ] Error: 1726 The remote\u2026","rel":"","context":"In "Windows 11"","block_context":{"text":"Windows 11","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-11\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":62563,"url":"https:\/\/www.winhelponline.com\/blog\/media-feature-pack-error-0x80070490\/","url_meta":{"origin":5957,"position":2},"title":"How to Fix Media Feature Pack Error 0x80070490","author":"Ramesh","date":"September 30, 2023","format":false,"excerpt":"When you use Optional Windows Features to install the Media Feature Pack Feature-on-demand component on Windows N or the KN Edition, the error 0x80070490 may appear. The error 0x80070490 denotes \"Element not found\" which indicates a problem in the COMPONENTS registry hive or missing files in the components store. When\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"media features pack FOD error 0x8070490","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/09\/mediafeatures-error-490.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/09\/mediafeatures-error-490.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/09\/mediafeatures-error-490.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":75466,"url":"https:\/\/www.winhelponline.com\/blog\/dism-error-3017-reboot-required\/","url_meta":{"origin":5957,"position":3},"title":"DISM Error 3017 “System reboot is required”","author":"Ramesh","date":"June 9, 2024","format":false,"excerpt":"When you run DISM ScanHealth or RestoreHealth to repair the component store, error 3017 may occur. The entire error message verbatim is given below: Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Image Version: 10.0.22631.3527 [== 4.9% ] Error: 3017 The requested operation failed. A system reboot is required to\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"pendingxmlidentifier","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/06\/pendingflags-components-hive.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/06\/pendingflags-components-hive.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/06\/pendingflags-components-hive.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/06\/pendingflags-components-hive.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":32018,"url":"https:\/\/www.winhelponline.com\/blog\/dism-error-1392-file-corrupted-unreadable\/","url_meta":{"origin":5957,"position":4},"title":"DISM Error 1392 – File or directory is corrupted","author":"Ramesh","date":"January 17, 2023","format":false,"excerpt":"When you run a DISM command to scan or repair the component store, the error code 1392 appears, and DISM quits. The full error message is mentioned below. Deployment Image Servicing and Management tool [== 3.8% ] Error: 1392 The file or directory is corrupted and unreadable. The DISM log\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"run chkdsk on system drive","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/01\/run-chkdsk-c-drive.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/01\/run-chkdsk-c-drive.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/01\/run-chkdsk-c-drive.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":31441,"url":"https:\/\/www.winhelponline.com\/blog\/error-0x800703e6-998-dism-windows-update\/","url_meta":{"origin":5957,"position":5},"title":"Errors 0x800703e6 (998) in DISM and Windows Update","author":"Ramesh","date":"January 2, 2023","format":false,"excerpt":"Symptoms Installing Windows Updates results in the error 0x800703e6 on a Windows 10 or 11 computer. The user is unable to install new updates or uninstall a previously installed update. Attempting to repair (in-place upgrade) the Windows installation using the Media Creation tool or the Update Assistant tool may fail\u2026","rel":"","context":"In "Windows 10"","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"cbscore.dll corrupt - file information","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2023\/01\/cbscore-dll-corrupted.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/5957","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/comments?post=5957"}],"version-history":[{"count":0,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/5957\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/media?parent=5957"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/categories?post=5957"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/tags?post=5957"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}