-And Windows Defender definitely has 32 & 64-bit versions so on a 64-bit machine, as they told you, you would not install/use the 32-bit version (unless it is within a 32bit virtual machine). It is also true that any other A/V you install on 32 or 64bit machines will disable Windows Defender, such as MSE that you mentioned.
"They" did not tell me to run the 64-bit version of Windows Defender. Why do you want to put words in their mouth that they never said? Let me set you straight:
MS tech support personnel were very emphatic about
not running Windows Defender with 64-bit Win7 Pro. Period. Indeed, as I stated previously, they gave me instructions and advice for
uninstalling Windows Defender entirely, although I never succeeded in my attempts to do that.
This evening I expect to wipe the new SSD and use the Digital River 64-bit Windows 7 Professional SP1 ISO. After the installation ends, I will check Task Manager to see whether Windows Defender is running, before I run the installer for MSE. If Windows Defender is running, then maybe that is the cause of some problems that I have encountered after installing and updating 64-bit Win7 Pro.
Fact: Just because a 64-bit version is installed does not mean that Windows will launch it instead of the 32-bit version which is also installed.
(1) Take a look at Program Files, then at Program Files (x86), and you will see the same MS applications are installed in each folder, such as Internet Explorer and Windows Defender.
(2) In fact, the Windows 7 installer adds the 32-bit Internet Explorer to the task bar, and the "Internet Explorer" entry on the Start Menu also launches the 32-bit executable. To use the 64-bit Internet Explorer 8 (for which MS ended support entirely this past April), you must find the executable, then launch it there and/or add it to the Start Menu, and/or create a desktop shortcut for it.
(3) After you launch 64-bit Internet Exporer, run Task Manager and you will see that the 64-bit process has launched a 32-bit I.E. "child" process (!). It would not surprise me in the least if the 64-bit Windows Defender executable also launches the 32-bit executable as a "chlid" process.
(4) If launching the 32-bit Windows Defender as a child process could lead to a problem(s), then it is understandable that the MS tech support people were so alarmed when I told them it had been installed. At least two of them declared that the installer was
not supposed to install Windows Defender on any 64-bit system because, if memory serves, they said that there was a problem with running 32-bit Windows Defender
in compatiblity mode. They, and I, even began to wonder whether I had a counterfeit Windows 7 Pro package.
Of course, if the only process running was the 64-bit Windows Defender executable perhaps there would not be a problem, but after it launches the 32-bit executable as a "child process" maybe a bug shows its presence.
Which leads to the question, one for which I will refrain from speculating as to the answer:
why does Trusted Installer install 32-bit executables of each application on a 64-bit system for which it also installs the 64-bit executables of the same applications?
Enough said. I have other things to do.
--- Stardance
nil carborundum illegitimi