xplorer2_uc.exe continues to run after I've closed Xplorer2

Discussion & Support for xplorer² professional

Moderators: fgagnon, nikos, Site Mods

Post Reply
jim28277
Member
Member
Posts: 9
Joined: 2008 Dec 29, 01:15
Location: Charlotte, NC U.S.A.

xplorer2_uc.exe continues to run after I've closed Xplorer2

Post by jim28277 »

Why does xplorer2_uc.exe continue to run after I've stopped running xplorer2? (something to do with accessing system files in the install) I know I've read the answer to my question before but i can't find it.
Best regards Jim
User avatar
johngalt
Gold Member
Gold Member
Posts: 568
Joined: 2008 Feb 10, 19:41
Location: 3rd Rock
Contact:

Post by johngalt »

Image

Image
jim28277
Member
Member
Posts: 9
Joined: 2008 Dec 29, 01:15
Location: Charlotte, NC U.S.A.

Post by jim28277 »

johngalt wrote:Might it be this topic?  http://forum.zabkat.com/viewtopic.php?t=7147
Thanks John. I'm not sure this is exactly where I read this in the fist place but the message was the same. I'm not sure why xplorer2 ever needs to "stay resident" but at least I know how I can over ride this feature with the registry editor. Cheers,
Best regards Jim
User avatar
nikos
Site Admin
Site Admin
Posts: 15831
Joined: 2002 Feb 07, 15:57
Location: UK
Contact:

Post by nikos »

it stays resident because next time you want to open a folder you want to do it faster, no?
jim28277
Member
Member
Posts: 9
Joined: 2008 Dec 29, 01:15
Location: Charlotte, NC U.S.A.

Post by jim28277 »

nikos wrote:it stays resident because next time you want to open a folder you want to do it faster, no?
Correct. Thank you.
Best regards Jim
AlanMintaka
Member
Member
Posts: 26
Joined: 2008 Jan 25, 11:04

Post by AlanMintaka »

nikos wrote:it stays resident because next time you want to open a folder you want to do it faster, no?
This caused a problem when I tried to install the update to version  1.8.0.1.  Even though I quit all instances of Xplorer before running the installation program, I got an error message saying the file "Xplorer2_UC.exe" could not be open for writing.  

The workaround was killing the process in Windows Task Manager and then running the installation again.  Shouldn't the installation program take care of this automatically by killing the process so no write access problem occurs?  Or am I doing something wrong?  

Have a good one,
Big Al Mintaka

OS: 5.0.0.2 ULT x64 4/27/2021
WIndows: 10 20H2 build 19042.928 Feature Experience Pack 120.2212.551.0
Dell Dimension 8400 3.2GHz 4GB RAM
Applications: The usual windows crap, minus Office
User avatar
nikos
Site Admin
Site Admin
Posts: 15831
Joined: 2002 Feb 07, 15:57
Location: UK
Contact:

Post by nikos »

the installation program does that but it will work only from now onwards
Post Reply