Task manager says 32 bit ver. Should it be 64 bit.
I have a Surface Pro 3 running Windows 10. I installed Webroot SecureAnyWhere, version says 184.108.40.206. Task Manager says Webroot is running in 32 bit mode. Did I do something wrong?
This topic has been closed for comments
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Welcome to the Community Forums.
No, you have done nothing wrong. As WSA covers both 32bit & 64bit systems but with only one installer it runs in 32bit mode. The reason for this is that 64-bit versions of Windows can run 32-bit software, but 32-bit versions of Windows can’t run 64-bit software.
For information, 64-bit Intel and AMD processors are backward compatible and can natively execute 32-bit software. The 32-bit WSA executable will run about the same as it would on a 32-bit version of Windows, so there’s no downside to running this on a 64- bit operating system.
Hope that helps?
Are there real-world technical limitations of a 32bit Webroot? It will have access to fewer registers, and some sort of memory limitations, but will any of that affect Webroot's ability to do its job properly?
The Microsoft standard for installing applications is to put 64bit code in "?:Program Files" and 32bit applications in "?:Program Files (x86)". Do we have any idea why Webroot did not follow this standard? There are similar standards for registry entries, but I did not look at the Webroot registry entries...
Reference (for certification, and I assume Webroot did not get the "Certified" stamp):
Welcome to the Community Forums.
1. Are there real-world technical limitations of a 32bit Webroot?
Not as far as I know, have heard, etc., and also I do not believe that Webroot would provide a 32bit
solution if it was any less secure than a 64bit one.
2. It will have access to fewer registers, and some sort of memory limitations, but will any of that affect
Webroot's ability to do its job properly?
Same reply as above...they would not produce a 32bit version if 64bit was better.
3. The Microsoft standard for installing applications...?
Good question...and that one I do not know the answer to other than to say...it does not really matter,
and there are many other app authors who do the same and/or allow the user to install where they wish
4. Reference (for certification,...?
I suspect not but then again most of the major players either do not have this or if they do they chose
not to make a big deal of it or even acknowledge it...so in my book it is fairly irrelevant. If the company is
reputable and produces a good product that works well then this is somewhat irrelevant.
Plus I suspect (but do not know) that MS may charge for the privilege certification...so another reason
for not bothering with this if that is indeed true.
But as you say for an official answer "Perhaps someone from Webroot could assist in answering if these questions"...so I will ping our Community Manager
For example, you can use filever.exe to check the file properties, and you will see this:
--a-- W32i APP ENU 220.127.116.11 shp 1,252,856 01-31-2018 wrsa.exe
You can also use Task Manager, enable the Platform column, and see it there:
32bit apps will run fine on 64bit Windows, but there are advantages to going 64bit. There are still unanswered questions as to when WebRoot will go 64bit, and why it installs in the wrong folder (it should install into "Program Files (x86)".
I would really like to see the app go 64bit and stay installed into the 64bit folder structure. If that is not possible for some reason, I think they should comply with Microsoft standards and install into the 32bit folder structure.
One downside to having only 32 bit is that it only seems to detect 4GB ram and says low ram every time you run the system analyzer.
That same issue appears here and this is the most likely cause.
Please start a new Thread. This Thread is 6 Years old. Thread Closed.