Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 589028" data-attributes="member: 32260">Prevent access to 16-bit applications.This option exists in most Windows versions, even in Windows 10 64Bit (at least Windows Server 2003).GPEDIT: Administrative Templates-Windows Components-Application Compatibility-Prevent access to 16-bit applications.Windows 64Bit has not got NTVDM subsystem, so 16Bit applications cannot run (yet, there are 64Bit NTVDM alternatives available on&nbsp; GitHub). Also, 32Bit applications that rely on 16Bit components will not run properly. In Windows 64Bit is possible to run 16Bit applications in 32Bit virtual machine or in DosBox (DOS emulator) - both works independently of VDMDisallowed settings made in Windows 64Bit.Registry settings:*********************************************************************************Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat]&quot;VDMDisallowed&quot;=dword:00000001*********************************************************************************There is also another registry key that can control 16Bits if the above key is absent.HKLM\System\CurrentControlSet\Control\WOW\!DisallowedPolicyDefaultIt is not easy to run 16Bit applications in Windows 10 32BitFirst, NTVDM subsystem must be installed:Programs and Features -&gt; Turn Windows Features on or off -&gt; Legacy Components -&gt; Enable NTVDMNext, legacy console (old Command Prompt) have to be activated:&quot;Command prompt&quot; &gt; Right click over the title &quot;Command prompt&quot; &gt; &quot;Properties&quot; &gt; &quot;Use legacy console (require relaunch)&quot; &gt; &quot;Accept&quot; &gt; close and re-open &quot;Command prompt&quot;.Disable 16Bits option will be added soon to Hard_Configurator.</blockquote>

[QUOTE="Andy Ful, post: 589028, member: 32260"] [B]Prevent access to 16-bit applications.[/B] This option exists in most Windows versions, even in Windows 10 64Bit (at least Windows Server 2003). GPEDIT: Administrative Templates-Windows Components-Application Compatibility-Prevent access to 16-bit applications. Windows 64Bit has not got NTVDM subsystem, so 16Bit applications cannot run (yet, there are 64Bit NTVDM alternatives available on GitHub). Also, 32Bit applications that rely on 16Bit components will not run properly. In Windows 64Bit is possible to run 16Bit applications in 32Bit virtual machine or in DosBox (DOS emulator) - both works independently of VDMDisallowed settings made in Windows 64Bit. Registry settings: ********************************************************************************* Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat] "VDMDisallowed"=dword:00000001 ********************************************************************************* There is also another registry key that can control 16Bits if the above key is absent. HKLM\System\CurrentControlSet\Control\WOW\!DisallowedPolicyDefault It is not easy to run 16Bit applications in Windows 10 32Bit First, NTVDM subsystem must be installed: Programs and Features -> Turn Windows Features on or off -> Legacy Components -> Enable NTVDM Next, legacy console (old Command Prompt) have to be activated: "Command prompt" > Right click over the title "Command prompt" > "Properties" > "Use legacy console (require relaunch)" > "Accept" > close and re-open "Command prompt". Disable 16Bits option will be added soon to Hard_Configurator. [/QUOTE]

Verification