Author Topic: Problems and/or caveats with 2.3.3.33  (Read 1607 times)

Offline Herschel

  • Newbie
  • *
  • Posts: 16
Problems and/or caveats with 2.3.3.33
« on: August 18, 2006, 02:14:54 AM »
I normally run Windows xp pro from a "user" account, and use "Run As" with a password to do administrative tasks (like installing new software).  CPF was totally non-functional after being installed this way-- I had to remove it (using rollback software, GoBack), reinstall CPF from an admin account, then reboot to an admin account, to get it going right. After that it runs fine from a user account. 
« Last Edit: August 18, 2006, 02:18:17 AM by Herschel »

Offline Eric Cryptid

  • Global Moderator
  • Comodo's Hero
  • *****
  • Posts: 2847
  • Security Saskquatch
Re: Problems and/or caveats with 2.3.3.33
« Reply #1 on: August 18, 2006, 02:47:57 AM »
A lot of programs require you to install the program using your Admin account especially if they need to add to or amend system files. It probably wasn't working when you installed it using your User Account because the Installer was not allowed to make the necessary changes to the registry etc. I'm on a User Account when I'm at work and it won't even let me install Quicktime fully because of the permissions set. Plus, installing it with your Admin account will make it available for use for all the User Accounts. I know it's annoying but unless you change that user to having Administrative rights then it's likely that future installed programs using your Client Account will have simular problems. Just one of those things about user accounts and those accounts with Administrative Rights.

Hope that helped.

Eric

Moderator: Any concerns? PM me and/or review the Forum Policy
System: 64 bit Win 10
Realtime Protection:CIS 12

Offline Herschel

  • Newbie
  • *
  • Posts: 16
Re: Problems and/or caveats with 2.3.3.33
« Reply #2 on: August 21, 2006, 03:44:40 AM »
I have the following problem with ver 2.3.3.33.

In windows xp pro, when I logoff an administrative account and logon to another account, I usually get a "crash" (crashrep.exe wants to run).

When this happens Process Explorer shows a CPF.exe still running under the previous administrative account, which apparently conflicts with it starting in the new account.

When I let crashrep.exe run, it kills the CPF.exe in the old account, but I usually end up with no CPF.exe running in either account.

This does not seem to happen when I logoff a non-admin account i.e. the CPF.exe running in a non-admin account seems to get replaced properly when I logoff and logon to another account (although crashrep.exe may still run).

My work-around is to always restart the computer when I want to change out of an account with administrative priviledges.

I get the folloing Event Viewer/Application entry after logging off from "Administrator":
-------------------------------------------------------
Event Type:   Information
Event Source:   UPHClean
Event Category:   None
Event ID:   1401
Date:      8/20/2006
Time:      11:38:53 PM
User:      BOB\Administrator
Computer:   BOB
Description:
The following handles in user profile hive BOB\Administrator (S-1-5-21-1715567821-1202660629-839522115-500) have been remapped because they were preventing the profile from unloading successfully:
 
cpf.exe (468)
  HKCU\Software\Classes (0x7c)
  HKCU\Software\Classes\CLSID (0x88)
  HKCU (0xc0)
  HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows (0x10c)
  HKCU\Software\Classes (0x134)
  HKCU\Software\Classes (0x180)
  HKCU\Software\Classes (0x210)
  HKCU\Software\Classes (0x224)
  HKCU\Software\Classes (0x240)
  HKCU\Software\Classes (0x258)
  HKCU\Software\Classes (0x26c)
---------------------------------------------------

Offline egemen

  • Comodo Staff
  • Comodo's Hero
  • *****
  • Posts: 3380
Re: Problems and/or caveats with 2.3.3.33
« Reply #3 on: August 21, 2006, 04:30:30 AM »
I have the following problem with ver 2.3.3.33.

In windows xp pro, when I logoff an administrative account and logon to another account, I usually get a "crash" (crashrep.exe wants to run).

When this happens Process Explorer shows a CPF.exe still running under the previous administrative account, which apparently conflicts with it starting in the new account.

When I let crashrep.exe run, it kills the CPF.exe in the old account, but I usually end up with no CPF.exe running in either account.

This does not seem to happen when I logoff a non-admin account i.e. the CPF.exe running in a non-admin account seems to get replaced properly when I logoff and logon to another account (although crashrep.exe may still run).


FYI: This crash issue has been fixed in the non-beta version of CF 2.3.

 

Free Endpoint Protection
Seo4Smf 2.0 © SmfMod.Com Smf Destek