XP Pro - aVast 4.6.6.23 Home - Limited User Problems

Hi,

First. Thank you. Second, I hope an answer to my question did not already exist on the board because I don’t want to be annoying to anyone who took great care to explain a solution to this problem already :slight_smile:

I looked very thoroughly and could not get an answer to the following.

  1. Ok, clean install of Windows XP Pro. Service Pack 2 and all updates.

  2. Clean install of Office 2003 and SP1

  3. Installed aVast logged on as ADMINISTRATOR (not an Admin account)

  4. Everything seems to be working ok. Perfectly when logged in with Administrator access.

  5. I setup a user for this new system and gave him only limited rights (I am setting this up for a client and I want to lock it down as reasonably as possible. Limited User access is very attractive and works fine other than with aVast.) Ok, so here is the error(s) I am getting. It’s clearly a right access (or rights related, lol) issue.

ERROR(S)

  1. ashDisp.exe - Application Error
    “The application failed to initialize propertly (0xc0000022). Click on OK to terminate the application.”

NOTES: Here is what I have tried. I hit OK and proceeded to enter as the Limited User. Everything is fine (it appears as though I am still be somewhat protected by at least those pieces that are running as “services”. My assumption is that “askDisp.exe” is simply the taskbar control and is not “critical” to my security.

a. Option 1 which I tried and it worked was to add a RunAs command in front:
RunAs /env /noprofile /savecred /user:blah\Administrator (pathtoashDisp.exe/ashDisp.exe) and it worked fine. Not what I call a proper solution and I don’t like having to do this. Not sure if its cool. (I added a password to protect the taskbar dilio for aVast.)

b. Option 2 (not tried, but considering). Yanking out the part in the registry which is calling this app to run. I don’t really need it (as far as I can tell) once I set things up. Again, not a preferred solution.

c. Option 3 - Registe with this forum and share what I have done and HOPEFULLY I can get this resolved so that my problem goes away and I can provide a Limited Access Account for my client’s system while running aVast without any popup errors.

NOTE2: The second error I get is when I run Outlook:

The add-in “C:\Program Files\Alwil Software\Avast4\ashOutXt.dll” could not be installed or loaded. This problem may be resolved by using Detect and Repair on the Help menu.


Again, the same type of problem as I am having when I logon with a Limited User account. (This Outlook error is also happening ONLY under the Limited User account. Just to clarify).

So:

Did I miss something?

Has anyone else had this problem?

HELP! Please HELP! Going mad… lol.

Thank you again for all of your help Evangelist. I read your most helpful posts. Sorry I couldn’t figure it out on my own :frowning:

Regards,

ClearlyTechnical

Ok,

It looks like a rights issue so far.

I took off Simple File Share, this allowed me to set permissions. (first time in XP, doh).

Just to make sure I covered all basis, I went to local policy editor and ran imported the template for the default settings as there were during initial install. Then I ran the configuration essentially resetting all my files (those installed during the initial install) to their original settings. (um, I think, lol)

Then I did the permission settings as stated above and then made sure I applied it to all child directs and objects, etc. (I did this on the C: drive itself. Gave full control, and then applied it to every dang file in the whole system, lol. Yes, I know that doesn’t help, but at least it looks like it’s a rights issue, hahah). Ok, now I am going to strip those rights off and try to apply to program files only. etc., process of elimination. I will present feedback when done.

Thanks all,

ClearlyTechnical …replies???

Ok, Looks like I may have solved this Scooby Doo Mystery. Not sure how, so feedback is very much welcomed.

Ok, here is what I think happened.

When I added the Limited User to the Permissions and had it propagate, I believe it restored the proper settings across the whole setting as they also related to Administrator rights.

Anyway, I am dead tired. I will re-address this tomorrow and refrain from trying to explain something when I am cross eyed, lol.

Good night and I look forward to the replies.

Support, if you could at least let me know the following, that WOULD REALLY HELP!!

  1. What files are accessed and where?

  2. What are the rights they need, what do they expect even for a limited user?

  3. What does aVast “touch” what does it want?

Thanks all,

ClearlyTechnical (aka ClearlyTired! lol)

Hi all,

Ok, just wanted to provide a little more feedback.

(Hope this helps support)

I made a new account called Test. Gave it Administrator privs.

Logged in, everything came up fine.

I then exited out, changed it to Limited User, logged back on, everything came up fine.

Clearly it appears to have been a rights issue. Rather than reconstructing the old logon account. I am just going to move the files to a new account that is cleanly installed.

Thanks for all the help and I look forward to the feedback. I am sure that someone can benefit from this, or at least I hope so, lol.

Ok, goodnight for sure now,

ClearlyTechnical

Hi all (and Support)

Here is the command I typed to clean up my system back to it’s default:

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose

I do the verbose to make sure it completes the 3800 or so changes.

If you are unable to complete the above command and it dumps you out, then you just have to give yourself rights to your ENTIRE system and make sure you apply them to all objects, etc.

Then run the above command and that will restore your systems rights back to where they should be.

I DO NOT RECOMMEND ANYONE TRY THIS WITHOUT FIRST THOROUGHLY UNDERSTANDING WHAT THEY ARE DOING!

Thanks,

ClearlyTechnical