You are here

Chrome Portable 64 showing as 32 bit in Task Manager Win 10

3 posts / 0 new
Last post
vinieux
Offline
Last seen: 2 months 5 days ago
Joined: 2011-03-17 05:07
Chrome Portable 64 showing as 32 bit in Task Manager Win 10

I have a laptop with Windows 10 pro on which I use Google Chrome Portable from Portable Apps. It helps me keep my browser settings and bookmarks on a key-chain pen drive because I travel quite a bit and have to use other people's computers.

Here's the problem. When I start it up and check Task Manager, it shows Google Chrome right on top under Apps with the number of processes it is running. But below that it shows another entry under Background Processes which says Google Chrome Portable (32 bit).

I can safely end this task and continue with my life. It makes no difference to my work, nor does it shut down Chrome when I end the task.

I have completely uninstalled Chrome (through the PA platform), deleted all Program Files and User folder references to Chrome and reinstalled Chrome to no effect. Even without a single extension or add on, and clean windows folders, this happens all over again.

By the way I am using the latest Test version of Portable Apps Chrome Portable 64 bit (67.0.3396.62 (Official Build) (64-bit)

Would anyone know why this is happening?

Ken Herbert
Ken Herbert's picture
Online
Last seen: 6 min 13 sec ago
DeveloperModerator
Joined: 2010-05-25 18:19
Necessary component

The *Portable.exe file is the component we build that handles portability for each app. By killing it, you are actually causing Chrome Portable to not be able to clean up after itself. Depending on the app, this can be catastrophic, or negligible, to the way it runs.

I personally don't know the inner workings of Chrome Portable at all so can't really comment on it, but I think as long as you are logged into Chrome you probably wouldn't notice much in the way of negative side effects from killing the portable exe file - but you really don't need to, and for other apps you should never do that.

It is a 32 bit process because there is no reason for us to build it as a 64 bit process - there is practically zero benefit from us trying it, so we don't.

the developer formerly known as winterblood

vinieux
Offline
Last seen: 2 months 5 days ago
Joined: 2011-03-17 05:07
Thank you

Thank you for your reply. I will stop ending the task right away.

Log in or register to post comments