- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Windows Xp Machine will not release pvxwin32.e xe from memory after MAS90 is closed
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-03-2010 02:55 PM
Hello,
I am currently trying to figure out why pvxwin32.exe stays in memory after MAS90 is closed. Only one machine has this behavior, It is a Windows Xp Professional machine connected to a Windows 2003 server. I have changed the memory, bought a new hard drive, reinstalled windows, reinstalled the MAS90 client, deleted the MAS90 user and recreated it and cannot for the life of me figure out why this machine has this behavior. During the day multiple copies of pvxwin32.exe get stuck in memory and have to be terminated from the task manager.
Re: Windows Xp Machine will not release pvxwin32.e xe from memory after MAS90 is closed
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-04-2010 06:30 AM
When you say you reinstalled windows, do you mean a totally clean install from scratch so that there are no leftovers from other programs being installed?
Sounds likely to be some software or driver being installed that is conflicting. Virus scanner maybe?
Sorry, I know this is a pretty broad suggestion.
Target System Technology, Inc. - Spokane, WA -
The best solution often comes not from answering the question asked, but understanding WHY the question was asked.


