How Windows 64-bit Supports 32-bit Applications

  • Thread starter Thread starter hjlbx
  • Start date Start date
Status
Not open for further replies.
Hi hjlbx with regards to antivirus software, are there limitations on all x 32 bit applications, and that's why the likes of Emsisoft and ESET produce a native x 64 bit application? I don't understand, when I downloaded Microsoft Business 365 it recommended the x 32 bit as the x 64 bit had limitations?
 
Hi hjlbx with regards to antivirus software, are there limitations on all x 32 bit applications, and that's why the likes of Emsisoft and ESET produce a native x 64 bit application? I don't understand, when I downloaded Microsoft Business 365 it recommended the x 32 bit as the x 64 bit had limitations?

The primary problem with Antivirus on 64-bit systems is Microsoft Patch Guard.

Kernel Patch Protection - Wikipedia, the free encyclopedia

Source: Wikipedia

Not sure about the limitations of 64-bit Microsoft Business 365.
 
Hi hjlbx with regards to antivirus software, are there limitations on all x 32 bit applications, and that's why the likes of Emsisoft and ESET produce a native x 64 bit application? I don't understand, when I downloaded Microsoft Business 365 it recommended the x 32 bit as the x 64 bit had limitations?
This is relevant to the security mechanisms in the x64 version of Windows.

Many AV applications rely on patching the kernel (core) of Windows in order for them to implement some advanced anti-malware features in your system.

However, there is a mechanism in x64 versions of Windows that prevents such modifications to the Windows kernel, which usually would cause those AV applications to break on x64 systems.
That is why AV companies are usually forced to redesign their products in order for them to work properly, and offer the same protection, in x64 Windows systems. Without changes in the internal design of their software, it is very likely that the software will not offer the same level of security.

This explains the need for, and the existence of, dedicated, native x64 versions of many security solutions.

EDIT: @hjlbx: Perfect ninja...
 
This is relevant to the security mechanisms in the x64 version of Windows.

Many AV applications rely on patching the kernel (core) of Windows in order for them to implement some advanced anti-malware features in your system.

However, there is a mechanism in x64 versions of Windows that prevents such modifications to the Windows kernel, which usually would cause those AV applications to break on x64 systems.
That is why AV companies are usually forced to redesign their products in order for them to work properly, and offer the same protection, in x64 Windows systems. Without changes in the internal design of their software, it is very likely that the software will not offer the same level of security.

This explains the need for, and the existence of, dedicated, native x64 versions of many security solutions.

EDIT: @hjlbx: Perfect ninja...

Online_Ninja = good handle
 
  • Like
Reactions: DracusNarcrym
Exactly, 32-bit operating systems can accept unsigned drivers that may in some cases create instability in the system, while with 64 bit this cannot happen because the installation takes place just in case the driver is certified and digitally signed by the developer. So, in the case of an antivirus, it is necessary that it install 64-bit driver specifically developed and, if they are not available, you cannot install the application.
 
Exactly, 32-bit operating systems can accept unsigned drivers that may in some cases create instability in the system, while with 64 bit this cannot happen because the installation takes place just in case the driver is certified and digitally signed by the developer. So, in the case of an antivirus, it is necessary that it install 64-bit driver specifically developed and, if they are not available, you cannot install the application.

When beta testing, always verify that the drivers have been digitally signed before attempting install on 64-bit system.

It is rare, but sometimes the vendor has not gone through the trouble of digitally signing the drivers - since, after all, it is a beta.

There is a way around it on some systems by disabling Secure Boot or UEFI.
 
When beta testing, always verify that the drivers have been digitally signed before attempting install on 64-bit system.

It is rare, but sometimes the vendor has not gone through the trouble of digitally signing the drivers - since, after all, it is a beta.

There is a way around it on some systems by disabling Secure Boot or UEFI.
Indeed, it is necessary to verify whether the application's drivers are going to be permitted by Windows to be installed on the system.

When not allowed to run, though, this usually results in the application not installing at all, thus preventing any potential risks afterwards.
 
  • Like
Reactions: Venustus
64 bit implementation for an Antivirus may undergone a lengthy of process but no reason because of its way that you can manage to develop through many ways.

+ The benefits of x64 Architecture is design to improve the security and its complexity.
 
  • Like
Reactions: DracusNarcrym
Status
Not open for further replies.