{"id":26759,"date":"2022-06-12T09:21:46","date_gmt":"2022-06-12T03:51:46","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=26759"},"modified":"2022-06-13T17:05:12","modified_gmt":"2022-06-13T11:35:12","slug":"autoruns-knowndlls-wow64cpu-wowarmhw-xtajit","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/autoruns-knowndlls-wow64cpu-wowarmhw-xtajit\/","title":{"rendered":"Autoruns: KnownDlls wow64cpu, wowarmhw, xtajit, wow64, wow64win Missing"},"content":{"rendered":"<p>The <a href=\"https:\/\/www.winhelponline.com\/blog\/?s=autoruns\">Sysinternals Autoruns<\/a> utility may highlight some entries in yellow, indicating to the user that some files (referenced in the <code>KnownDLL<\/code> registry key) are missing from the system. The file names are below:<\/p>\n<ul>\n<li>C:\\Windows\\Syswow64\\wow64cpu.dll (<code>_wow64cpu<\/code>)<\/li>\n<li>C:\\Windows\\System32\\wowarmhw.dll (<code>_wowarmhw<\/code>)<\/li>\n<li>C:\\Windows\\Syswow64\\wowarmhw.dll\u00a0(<code>_wowarmhw<\/code>)<\/li>\n<li>C:\\Windows\\System32\\xtajit.dll (<code>_xtajit<\/code>)<\/li>\n<li>C:\\Windows\\Syswow64\\xtajit.dll\u00a0(<code>_xtajit<\/code>)<\/li>\n<li>C:\\WINDOWS\\Syswow64\\wow64.dll (<code>wow64<\/code>)<\/li>\n<li>C:\\WINDOWS\\Syswow64\\wow64win.dll (<code>wow64win<\/code>)<\/li>\n<\/ul>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-26760\" src=\"https:\/\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/06\/autoruns-knowndlls-missing.png\" alt=\"autoruns knowndlls missing\" width=\"901\" height=\"238\" srcset=\"https:\/\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/06\/autoruns-knowndlls-missing.png 901w, https:\/\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/06\/autoruns-knowndlls-missing-768x203.png 768w\" sizes=\"auto, (max-width: 901px) 100vw, 901px\" \/><\/p>\n<p><em>(The warning appears regardless of the version\/<a href=\"https:\/\/www.winhelponline.com\/blog\/find-out-if-a-program-exe-file-is-32-bit-or-64-bit\/\">bitness<\/a> of Autoruns you&#8217;re running &#8212; Autoruns.exe or Autoruns64.exe)<\/em><\/p>\n<p>The known DLLs on the computer are populated in the following registry key in Windows:<\/p>\n<pre>HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\KnownDLLs<\/pre>\n<p>The files referenced under the <code>KnownDLLs<\/code> key can be loaded only from the <code>C:\\Windows\\System32<\/code> or <code>C:\\Windows\\Syswow64<\/code> folders. In other words, the KnownDLLs registry key prevents DLLs from being loaded from the applications folder.\u00a0It&#8217;s a security measure that prevents bogus\/rogue copies of core system DLLs from being loaded from an applications folder.<\/p>\n<h2>Autoruns: KnownDlls wow64cpu, wowarmhw, wow64, xtajit, wow64win Missing<\/h2>\n<p><em>Why does Autoruns show that some KnownDLLs are missing? Are these files supposed to be present?<\/em><\/p>\n<p>The yellow-highlighted entries in Autoruns&#8217;s &#8220;KnownDLLs&#8221; tab (as shown in the above image) are WOW64 emulator modules. The WOW64 emulator consists of the following DLLs:<\/p>\n<ol>\n<li>Wow64.dll<\/li>\n<li>Wow64Win.dll<\/li>\n<li>Wow64Cpu.dll (x64 only)<\/li>\n<li>IA32Exec.bin (Intel Itanium only)<\/li>\n<li>Wowia32x.dll (Intel Itanium only)<\/li>\n<li>xtajit.dll (ARM64 only)<\/li>\n<li>wowarmw.dll (ARM64 only)<\/li>\n<\/ol>\n<p>As you see, some files are meant to be on 64-bit systems only, and others are supposed to be available only on ARM64 systems.<\/p>\n<p>The Windows-On-Windows-64 (WOW64) support DLLs are present only in the System32 directory and Autoruns will report \u201cfile not found\u201d for the corresponding SysWOW64 directory entries. <strong>This is normal<\/strong>.<\/p>\n<p>The <code>KnownDLLs<\/code> registry location doesn&#8217;t mention the directory path for the DLLs ( i.e., <code>C:\\Windows\\System32<\/code> or <code>C:\\Windows\\SysWOW64<\/code>), as you can see from the screenshot below:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-26761\" src=\"https:\/\/www.winhelponline.com\/blog\/wp-content\/uploads\/2022\/06\/knowndlls-registry-key.png\" alt=\"autoruns knowndlls missing\" width=\"601\" height=\"723\" \/><\/p>\n<p>For each entry\/file listed under the above registry key, Autoruns simply looks if the files are in <code>System32<\/code> and <code>SysWOW64<\/code> folders. Some DLLs are missing from the <code>System32<\/code> path because they are only 32-bit files (and so are in the <code>SysWOW64<\/code> folder), while others are 64-bit and are in the <code>System32<\/code> folder. Some files are missing on 32-bit and 64-bit computers because they are supposed to be only on ARM64-based systems.<\/p>\n<p>Whereas Windows ships with both 32-bit and 64-bit versions of a file (such as <code>advapi32.dll<\/code>). However, it&#8217;s not necessary that there should be a 32-bit version equivalent for every 64-bit module, or vice versa. You <strong>don&#8217;t<\/strong> need to run <a href=\"https:\/\/www.winhelponline.com\/blog\/repair-windows-10-using-dism-sfc\/\">DISM or SFC<\/a> for this.<\/p>\n<p>Therefore, you can safely ignore the Autoruns &#8220;File not found&#8221; warning (yellow highlighting of the WOW emulator files) in the <code>KnownDLLs<\/code> tab.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Sysinternals Autoruns utility may highlight some entries in yellow, indicating to the user that some files (referenced in the KnownDLL registry key) are missing from the system. The file names are below: C:\\Windows\\Syswow64\\wow64cpu.dll (_wow64cpu) C:\\Windows\\System32\\wowarmhw.dll (_wowarmhw) C:\\Windows\\Syswow64\\wowarmhw.dll\u00a0(_wowarmhw) C:\\Windows\\System32\\xtajit.dll (_xtajit) C:\\Windows\\Syswow64\\xtajit.dll\u00a0(_xtajit) C:\\WINDOWS\\Syswow64\\wow64.dll (wow64) C:\\WINDOWS\\Syswow64\\wow64win.dll (wow64win)<\/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":[6],"tags":[56],"class_list":["post-26759","post","type-post","status-publish","format-standard","hentry","category-utilities","tag-autoruns"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1252,"url":"https:\/\/www.winhelponline.com\/blog\/error-no-such-interface-supported-personalize-option-windows-7\/","url_meta":{"origin":26759,"position":0},"title":"Error &#8220;No such interface supported&#8221; when Accessing Personalize Context Menu Option in Windows 7","author":"Ramesh","date":"September 26, 2013","format":false,"excerpt":"When you right-click on the Desktop and choose Personalize, the error \"No such interface supported\" is shown and the Personalize window doesn't load.Registering the file actxprxy.dll resolves the problem. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.Type the following\u2026","rel":"","context":"In &quot;Windows 7&quot;","block_context":{"text":"Windows 7","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-7\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/archived2\/personalize-actxprxy.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":235,"url":"https:\/\/www.winhelponline.com\/blog\/error-there-is-no-script-engine-for-file-extension-when-running-vbs-files\/","url_meta":{"origin":26759,"position":1},"title":"[Fix] Can&#8217;t find Script Engine Vbscript, and &#8220;no script engine for .vbs&#8221;","author":"Ramesh","date":"April 27, 2008","format":false,"excerpt":"When you run a VBScript or .msi setup file that runs a VBScript, you may receive one of the following errors: Can't find script engine \"VBScript\" for script C:\\ProgramData\\Microsoft\\Windows\\OFFICEICON.vbs There is no script engine for file extension \".vbs\". This happens if the vbscript.dll module is not registered correctly or the\u2026","rel":"","context":"In &quot;Windows&quot;","block_context":{"text":"Windows","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":80435,"url":"https:\/\/www.winhelponline.com\/blog\/directx-runtime-component-required-game-error\/","url_meta":{"origin":26759,"position":2},"title":"&#8220;DirectX Runtime&#8221; component required when running a game","author":"Ramesh","date":"March 10, 2026","format":false,"excerpt":"When you run a game that requires the DirectX 2010 runtimes, the following error may occur. The following component(s) are required to run this program: DirectX Runtime RELATED: How to Fix Epic Games Launcher Error 0xC000007B or 0xC000012F Resolution Option 1: Install the DirectX Runtimes (June 2010) Download the DirectX\u2026","rel":"","context":"In &quot;Windows 10&quot;","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"directx runtimes components required when running a game","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/directx-runtime-needed-error.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":3105,"url":"https:\/\/www.winhelponline.com\/blog\/troubleshoot-explorer-crashes-checklist\/","url_meta":{"origin":26759,"position":3},"title":"Explorer.exe Crash Troubleshooting Tips","author":"Ramesh","date":"May 12, 2016","format":false,"excerpt":"Does Explorer crash and restart when you open a folder window or right-click a file or folder? This post tells you how to troubleshoot Explorer crashes which sometimes seriously affect our workflow. When the Explorer shell crashes, the taskbar vanishes, and the desktop remains blank for a moment while the\u2026","rel":"","context":"In &quot;Windows&quot;","block_context":{"text":"Windows","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2016\/05\/explorer-crash-1.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2016\/05\/explorer-crash-1.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2016\/05\/explorer-crash-1.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":80375,"url":"https:\/\/www.winhelponline.com\/blog\/api-ms-win-core-winrt-l1-1-0-dll-is-missing\/","url_meta":{"origin":26759,"position":4},"title":"[Fix] api-ms-win-core-winrt-l1-1-0.dll is missing (Adobe Acrobat Reader)","author":"Ramesh","date":"March 2, 2026","format":false,"excerpt":"Since the Feb 2026 update of Adobe Acrobat Reader, Windows 7 users receive the following error when opening a PDF or the Adobe Acrobat Reader app. You wonder how to get the missing api-ms-win-core-winrt-l1-1-0.dll file. AcroRd32.exe - System Error The program can't start because api-ms-win-core-winrt-l1-1-0.dll is missing from your computer.\u2026","rel":"","context":"In &quot;Windows 7&quot;","block_context":{"text":"Windows 7","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-7\/"},"img":{"alt_text":"adobe reader update scheduled task - stop and disable","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/disable_adobe_update_task.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/disable_adobe_update_task.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/disable_adobe_update_task.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2026\/03\/disable_adobe_update_task.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":69101,"url":"https:\/\/www.winhelponline.com\/blog\/xna-framework-4-error-2147024703\/","url_meta":{"origin":26759,"position":5},"title":"Microsoft XNA Framework 4.0 Setup error (-2147024703)","author":"Ramesh","date":"January 1, 2024","format":false,"excerpt":"When you install the Microsoft XNA Framework 4.0 (xnafx40_redist.msi) package, the setup may encounter the following error: Module C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\XNA\\Framework\\Shared\\xnavisualizer.dll failed to register. HRESULT -2147024703. Contact your support personnel. Cause The error -2147024703 (hex: 0x800700C1) means ERROR_BAD_EXE_FORMAT (the file is not a valid Win32 application). To register\u2026","rel":"","context":"In &quot;Windows 10&quot;","block_context":{"text":"Windows 10","link":"https:\/\/www.winhelponline.com\/blog\/category\/microsoft\/windows\/windows-10\/"},"img":{"alt_text":"xna framework 4.0 setup error -2147024703","src":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/01\/xna-framework-xnavisualizer-dll-error.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/01\/xna-framework-xnavisualizer-dll-error.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.winhelponline.com\/blog\/wp-content\/uploads\/2024\/01\/xna-framework-xnavisualizer-dll-error.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/26759","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=26759"}],"version-history":[{"count":0,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/posts\/26759\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/media?parent=26759"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/categories?post=26759"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.winhelponline.com\/blog\/wp-json\/wp\/v2\/tags?post=26759"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}