Update: An anonymous tipster has posted a small script (http://www.mobileread.com/forums/showpost.php?p=5960&postcount=44) to stop Wisptis from loading - it's small and clean, so I attached it here as well (script.zip). Either solution should work.

January 6th, 2004

(instruction also downloadable below)

The first time after I had installed Microsoft Office 2003, I noticed that whenever I run Adobe Acrobat Reader 6.0, a background process is started called wisptis.exe. Once wisptis.exe has been started, it won't stop unless you kill it or reboot your system.

In general, the ways in which wisptis.exe can get installed on your system:

installing Journal Viewer via Windows Update
installing Microsoft Office 2003

So what is wisptis.exe? A quote from TabletPCDeveloper.com:
Wisptis.exe (\Windows\System32) This executable runs as a system
service that provides pen-data collection for other components of the
SDK. When a component needs to interact with the pen (for example, to
collect ink or to detect gestures), this executable is spawned as a
service to communicate directly with the input device. On a Tablet PC,
Wisptis.exe interacts with the digitizer, whereas on a desktop it
interacts with the mouse as well. The executable’s name is an acronym
that references an outdated internal name for the team that developed it
(Windows Ink Services Platform Tablet Input Subsystem).
Well I don't have a Tablet PC and I certainly don't want an unnecessary process eating up my memory resources.

You cannot get rid of wisptis.exe by renaming or deleting it: Windows File Protection would cause it to reinstall the next time you run Adobe Acrobat.

There is even a rumor about a bug in wisptis.exe itself whereby it keeps part of the current user registry hive locked, preventing updates and eventually resulting in a corruption of the registry hive (which as reported leads to a "Userenv event 1517" on logging off or shutting down).

Others reported GDI leaks and CPU hogging. I haven't noticed the latter but can confirm that at one point, the number of open GDI handles by wisptis.exe was above 1000, which is unacceptable.

So by and large it seems wisptis.exe can make a thorough nuisance of itself.

To uninstall wisptis and Microsoft's Tablet PC Components on your PC, you must delete the following registry entries:

HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}
HKEY_CLASSES_ROOT\AppID\wisptis.EXE
HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}
HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}
HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}
HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}
HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}
HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}
HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}
HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}
HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}
HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}
HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}
HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}
HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}
HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}
HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}
HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}
HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}
HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}
HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}
HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}
HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}
HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}
HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}
HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}
HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}
HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}
HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}
HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}
HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}
HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}

HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden

HKEY_CLASSES_ROOT\TpcCom.* (all of them)

HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}
HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}
HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}
HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden

Now you can also safely delete \Windows\System32\Wisptis.exe. Make sure the process is not running; otherwise kill it before deletion.

Fully tested on an up-to-date Windows XP SP1.

Cheers,
Alex

Hay-seuss, what a pain in the butt! M$ sucks.

I've noticed that there's some kind of similar thing (if I understand it correctly) that happens when you use IE. So I just avoid IE as much as possible. Unfortunately you don't have that option here.

A tip: To find all the HKEY_CLASSES_ROOT\CLSID\* entries to be deleted, search for "WISPHidden" in the registry editor.

Thats really cool! Nothing I tried to get rid of this pain worked, until I followed your instruction.

Thanks a lot!

Could someone write an automated .inf Script for this and attach it to this thread?

In the meantime, I will try it myself...

Beamer

A tip: To find all the HKEY_CLASSES_ROOT\CLSID\* entries to be deleted, search for "WISPHidden" in the registry editor.

But make sure you don't search for "Whole Word Only".

Could someone write an automated .inf Script for this and attach it to this thread?
Attached you find such a script file.

You must rename it to unwisp.inf first, then right-click on the file and choose install. Use at your own risk ;)

Btw, if someone has not yet removed wisptis from his/her system, could you please open your registry and look up all

HKEY_CLASSES_ROOT\TpcCom.*

subkeys and post the names for .* here? I have them already removed, but would like to know the keys so that I can also include them in the .inf script.

Another note: If you are truly paranoid about removing wisptis, know that you can always deinstall Journal Viewer or Microsoft Office 2003, and reinstall either one to have the ugly wisptis process back on your system -- or turn on Win XP's System Restore feature prior to applying the changes.

Alex

Btw, if someone has not yet removed wisptis from his/her system, could you please open your registry and look up all

HKEY_CLASSES_ROOT\TpcCom.*

subkeys and post the names for .* here? I have them already removed, but would like to know the keys so that I can also include them in the .inf script.



On my XPSP1 system with Office 2003:

ClassicW
ClassicW.1
DrawAttrs
DrawAttrs.1
DrawAttrsXP
DrawAttrsXP.1
GenericRecognizer
GenericRecognizer.1
InkObject
InkObject.1
InkObjectXP
InkObjectXP.1
InkSettings.1
Lattice.1
RecoManager
RecoManager.1
TabletManager
TabletManager.1
UserDictionary
UserDictionary.1

On my XPSP1 system with Office 2003...Thanks a lot. Turns out these registry entries, though part of MS's tablet services, need not be deleted to keep wisptis from starting.

A tip: To find all the HKEY_CLASSES_ROOT\CLSID\* entries to be deleted, search for "WISPHidden" in the registry editor.

Excellent solution! One note on the registry search. On my XP Home machine, the WISPHidden, tried both ways, produced nothing. But using WISP produced the entire list of keys (and sub-keys).

For what it's worth, I didn't install Office2003 - just Access 2003.

Thanks again, Mike

Attached you find such a script file.
Seems to have worked perfectly! Thanks!

because it works, then you can kill wisptis.exe right after. Worked on XP home edition and windows server 2003

because it works, then you can kill wisptis.exe right after. Worked on XP home edition and windows server 2003
But it doesn't really help to kill acrord32.exe and wisptis.exe, if the next time you run acrord32.exe, wisptis is loaded again (windows file protection). Killing it each time you start Adobe Acrobat would be just a pain in the butt.

To prevent the MS Tablet PC Ink Pen components to start up, I just unregistered them.

I created an XP batch file like this:

rem -- UnRegister MS XP Tablet PC Ink Pen components
set sys32=%SystemRoot%\System32
set pfcfink=%CommonProgramFiles%\Microsoft Shared\INK
"%sys32%\WispTis.exe" /unregserver
"%sys32%\regsvr32.exe" /u "%sys32%\inked.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%/inkobj.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%/inkdiv.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%/tpcps.dll"
set pfcfink=
set sys32=
pause

In my PC, the components were installed by the MS Visio 2003 Viewer. That program uses an MS Installer Database (MSI), so whenever I would "Repair" such an Office program, the Tablet components get reregistered again.

To prevent the MS Tablet PC Ink Pen components to start up, I just unregistered them.I haven't tried it yet, but it definitely sounds good!

I found this page when I searched Google to find out why a process called wisptis used more than 5800 GDI objects on my system. And then it turns out the process is completely unessecary. Lol! :)

The deregistering method works fine :)
Thx for the batch file

Attached you find the batch file to unregister the MS Ink components. You have to remove .txt before running it. Credits go to SecureUser ;)

Like a few others here i Googled the wisptis and found this site. Just want to say thanks for the info and the scripts to rid my self of these un needed items. both scripst seem to have worked perfectly on my XP pro system

again Thanks

Jay

I just found this post from a Google search for "wisptis.exe". I had installed Adobe Reader earlier today and just noticed that program running. Just thought I'd mention that -- I have no Microsoft office software of any type installed. It clearly came with the Adobe package.

Hi all,

just found a simpler solution to this M$ annoyance; this is what I did:

1) disabled (many, many, many time ago) the prefetch mechanism;
2) renamed "wisptis.exe" in something different;
3) created a zero byte length "wisptis.exe" (you can, for instance, create an empty text document and rename it)

Now when I run Acrobat Reader, I have no more "wisptis.exe" in memory and the Office 2003 installation program don't start to reinstall it!


bye
m++

1) disabled (many, many, many time ago) the prefetch mechanism;
2) renamed "wisptis.exe" in something different;
3) created a zero byte length "wisptis.exe" (you can, for instance, create an empty text document and rename it)

Interesting! But I think you meant the windows file protection instead of the prefetch mechanism, right?

Interesting! But I think you meant the windows file protection instead of the prefetch mechanism, right?

No, I mean exactly the "Prefetch mechanism"; another M$ annoyance!

Once disabled, wisptis.exe cannot be reloaded in this way.

Anyway, I think that if you remove the wisptis.exe entry from the prefetch directory you can obtain the same result.

bye
m++

If you start up te task manager, you can close IEXPLORE.exe, and rthen re access the internet, I often do the same with EXPLORER.exe as it hogs resourses, then Click New Task, and run EXPLORER.exe again and it has few resourses to it!

Hay-seuss, what a pain in the butt! M$ sucks.

I've noticed that there's some kind of similar thing (if I understand it correctly) that happens when you use IE. So I just avoid IE as much as possible. Unfortunately you don't have that option here.

I also recommend something like TaskInfo (http://www.iarsn.com) which can display alerts if CPU resource used exceed a specified level.

Uninstall the Microsoft Windows Journal Viewer (It is one of the Windows Updates, but it is listed in your Add/Remove Programs list). Also, if you have done that already or never installed it to begin with, but you Microsoft Office 2003:
1) Go to Add/Remove Programs list
2) Click on Microsoft Office 2003 and click on "Change"
3) Select "Add or Remove Features" and click "Next
4) Check next to "Choose advanced customization of features" and click "Next"
5) Expand "Office Shared Features" and then "Alternative User Input"
6) Choose "Not Available" for "Handwriting"
7) Click on "Update" and click on "Ok" when it has finished
8) Restart your computer. The Wisptis.exe program should no longer be running once you have restarted.

I noticed a problem with the instructions you offer in the text file. I am not that knowlegeable of registry stuff but your instructions point to

HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden

and in my registry, they are

HKEY_CLASSES_ROOT\Installer\Features\9040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\9040110900063 D11C8EF10054038389C\WISPHidden

also in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden

it appears as

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040110900063D11C8EF10054038389C\Featu res\WISPHidden

The 7's should be 9's at the start of the folder

I used SecureUser's batch file and it works great on Windows 2000 SP4 with Office 2003 and Acrobat 6.

I noticed a problem with the instructions you offer in the text file. I am not that knowlegeable of registry stuff but your instructions point to
[...]
The 7's should be 9's at the start of the folder
Buz, the difference in your case appears to be in the /installer/ entries. While I added those to the list for completeness, they are not really necessary to be removed. Important is that you can delete the CLSID entries. Or, as mentioned before, use SecureUser's method (http://www.turcic.com/forums/showpost.php?p=5610&postcount=18), which was reported to me to work fine.

Alex

To prevent the MS Tablet PC Ink Pen components to start up, I just unregistered them.


Worked for me. Thanks.

Or you could just install the journal viewer. :)

installed adobe 6 yesterday and noticed the process today. killed it. and the journal viewer is uninstalled.

thanks.

just DONT INSTALL alternate text input LAMERs :)

Well , I noticed this "wisptis.exe" and thought to myself "I'll check on that little bugger"
:p
I decided to just un-install the " Microsoft Windows Journal Viewer " via "add remove programs"
Hopefully this will get rid of wisptis.exe and all the reg entries aswell.

Only usefull if that's how you got wisptis.exe installed in the first place, just thought I'd point it out , in case people overlooked it.

"wisptis.exe" is directly related to the Windows Journal Viewer.

This worked for me (deleting "Wisptis.exe"):

1) Download the setup file for Windows Journal Viewer here:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=fad44098-8b73-4e06-96d4-d1eb70eacb44

2) Search for "wisptis.exe" and delete everything you see related to it (including a prefetch file. Dunno if this is important, but I deelted everythin related to wiptis.exe)

3) Run it, but choose UNINSTALL\REMOVE.

4) After, try to run any Acrobat app. You should not see any "wisptis.exe" in your taskbar.

5) Obviously, my windows update shows Windows Journal Viewer when searching for updates. But just don't install it.

G' luck!

U guys are great!!!

Thanks a lot!

I used the CMD script, and it appears to have been successful, I found this from a google when I wondered what WISPITS.exe was also, thanks very much guys, you rule :D

While not as elegant.... for those that don't like getting into the registry here is what I did following the advice of the knowledgeable people here

created Wisptis.txt in windows\system32 folder using notepad
renamed wisptis.exe to wisptis.old in windows\system32 folder
renamed Wisptis.txt to wisptis.exe

and when I rebooted and launched Acrobat.... no Wisptis

( why on earth did Adobe include this ... Reader 6 is a mess - just look a the size of it - a 30 meg memory req just to browse a PDF!)

Thanks to everybody here for their help

Thanks A lot Yout solution works Excellent.


January 6th, 2004

(instruction also downloadable below)

The first time after I had installed Microsoft Office 2003, I noticed that whenever I run Adobe Acrobat Reader 6.0, a background process is started called wisptis.exe. Once wisptis.exe has been started, it won't stop unless you kill it or reboot your system.

In general, the ways in which wisptis.exe can get installed on your system:

installing Journal Viewer via Windows Update
installing Microsoft Office 2003

So what is wisptis.exe? A quote from TabletPCDeveloper.com:

Well I don't have a Tablet PC and I certainly don't want an unnecessary process eating up my memory resources.

You cannot get rid of wisptis.exe by renaming or deleting it: Windows File Protection would cause it to reinstall the next time you run Adobe Acrobat.

There is even a rumor about a bug in wisptis.exe itself whereby it keeps part of the current user registry hive locked, preventing updates and eventually resulting in a corruption of the registry hive (which as reported leads to a "Userenv event 1517" on logging off or shutting down).

Others reported GDI leaks and CPU hogging. I haven't noticed the latter but can confirm that at one point, the number of open GDI handles by wisptis.exe was above 1000, which is unacceptable.

So by and large it seems wisptis.exe can make a thorough nuisance of itself.

To uninstall wisptis and Microsoft's Tablet PC Components on your PC, you must delete the following registry entries:

HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}
HKEY_CLASSES_ROOT\AppID\wisptis.EXE
HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}
HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}
HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}
HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}
HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}
HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}
HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}
HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}
HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}
HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}
HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}
HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}
HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}
HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}
HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}
HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}
HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}
HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}
HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}
HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}
HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}
HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}
HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}
HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}
HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}
HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}
HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}
HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}
HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}
HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}

HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden

HKEY_CLASSES_ROOT\TpcCom.* (all of them)

HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}
HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}
HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}
HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden

Now you can also safely delete \Windows\System32\Wisptis.exe. Make sure the process is not running; otherwise kill it before deletion.

Fully tested on an up-to-date Windows XP SP1.

Cheers,
Alex

Thanks A lot Yout solution works Excellent.

And by that i mean nerds in the good sence of the word, i hope i can be as good as you some day! ;)

Thanks

that was a mistake, my apologies to the author.

admin edit: no problem, I removed your previous post.

Hi there !

I found also a Registry Entry in

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Usage \WISPHidden

May I also delete this entry ???

Wisptis.exe was deleted and also NOT running !

Thx , Guido

January 6th, 2004

(instruction also downloadable below)

The first time after I had installed Microsoft Office 2003, I noticed that whenever I run Adobe Acrobat Reader 6.0, a background process is started called wisptis.exe. Once wisptis.exe has been started, it won't stop unless you kill it or reboot your system.

In general, the ways in which wisptis.exe can get installed on your system:

installing Journal Viewer via Windows Update
installing Microsoft Office 2003

So what is wisptis.exe? A quote from TabletPCDeveloper.com:

Well I don't have a Tablet PC and I certainly don't want an unnecessary process eating up my memory resources.

You cannot get rid of wisptis.exe by renaming or deleting it: Windows File Protection would cause it to reinstall the next time you run Adobe Acrobat.

There is even a rumor about a bug in wisptis.exe itself whereby it keeps part of the current user registry hive locked, preventing updates and eventually resulting in a corruption of the registry hive (which as reported leads to a "Userenv event 1517" on logging off or shutting down).

Others reported GDI leaks and CPU hogging. I haven't noticed the latter but can confirm that at one point, the number of open GDI handles by wisptis.exe was above 1000, which is unacceptable.

So by and large it seems wisptis.exe can make a thorough nuisance of itself.

To uninstall wisptis and Microsoft's Tablet PC Components on your PC, you must delete the following registry entries:

HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}
HKEY_CLASSES_ROOT\AppID\wisptis.EXE
HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}
HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}
HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}
HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}
HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}
HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}
HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}
HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}
HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}
HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}
HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}
HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}
HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}
HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}
HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}
HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}
HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}
HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}
HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}
HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}
HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}
HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}
HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}
HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}
HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}
HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}
HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}
HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}
HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}
HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}

HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden

HKEY_CLASSES_ROOT\TpcCom.* (all of them)

HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}
HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}
HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}
HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden

Now you can also safely delete \Windows\System32\Wisptis.exe. Make sure the process is not running; otherwise kill it before deletion.

Fully tested on an up-to-date Windows XP SP1.

Cheers,
Alex

Check with the Gentlemen who was kind enough to post such a detailed doc. he will most certainly guide you in the right direction. Again, my apologies to the author and my thanks for a mst detailed and precise explanation. It worked for me. Thanks,

Laz

This worked great for me, but here on Win2k SP4 I had to modify the script a little:

rem -- UnRegister MS Tablet PC Ink Pen components
set sys32=%SystemRoot%\System32
set pfcfink=%CommonProgramFiles%\Microsoft Shared\Ink
"%sys32%\WispTis.exe" /unregserver
"%sys32%\regsvr32.exe" /u "%sys32%\inked.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%\InkObj.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%\gdiplus.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%\tpcps.dll"
rem "%sys32%\regsvr32.exe" /u "%pfcfink%\inkdiv.dll"
set pfcfink=
set sys32=
pause

For those of you complaining that Acrobat Reader 6 is slow, there's a little program here:

http://www.tnk-bootblock.co.uk/prods/misc/index.php

called ARSpeedUp that will really decrease load times. It disables almost all of the useless plug-ins that come with reader. More info at the site.

Cheers!

Btw, if someone has not yet removed wisptis from his/her system, could you please open your registry and look up all

HKEY_CLASSES_ROOT\TpcCom.*

subkeys and post the names for .* here? I have them already removed, but would like to know the keys so that I can also include them in the .inf script.



On my XPSP1 system with Office 2003:

ClassicW
ClassicW.1
DrawAttrs
DrawAttrs.1
DrawAttrsXP
DrawAttrsXP.1
GenericRecognizer
GenericRecognizer.1
InkObject
InkObject.1
InkObjectXP
InkObjectXP.1
InkSettings.1
Lattice.1
RecoManager
RecoManager.1
TabletManager
TabletManager.1
UserDictionary
UserDictionary.1

This is what I had for TCPCOM; installed is WinOff2003, and Wacom Tablet.

RegSafe Report Header
--------------------------------

List Of Find All : "TPCCOM"
KEY: [HKEY_CLASSES_ROOT\TpcCom.ClassicW][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.ClassicW.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.DrawAttrs][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.DrawAttrs.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.InkObject][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.InkObject.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.InkObjectXP][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.InkObjectXP.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.InkSettings.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.Lattice][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.Lattice.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.RecoManager][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.RecoManager.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.TabletManager][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.TabletManager.1][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.UserDictionary][][]
KEY: [HKEY_CLASSES_ROOT\TpcCom.UserDictionary.1][][]

My HJT Dump:

Logfile of HijackThis v1.97.7
Scan saved at 11:54:16 PM, on 2/22/2004
Platform: Windows XP SP1 (WinNT 5.01.2600)
MSIE: Internet Explorer v6.00 SP1 (6.00.2800.1106)

Running processes:
C:\WINDOWS\System32\smss.exe
C:\WINDOWS\system32\winlogon.exe
C:\WINDOWS\system32\services.exe
C:\WINDOWS\system32\lsass.exe
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\System32\svchost.exe
C:\Program Files\Common Files\Symantec Shared\ccSetMgr.exe
C:\Program Files\Common Files\Symantec Shared\ccEvtMgr.exe
C:\WINDOWS\system32\spoolsv.exe
C:\WINDOWS\system32\netdde.exe
C:\Program Files\Common Files\Adobe Systems Shared\Service\Adobelmsvc.exe
C:\Program Files\Common Files\Symantec Shared\ccProxy.exe
C:\WINDOWS\System32\dllhost.exe
C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\MDM.EXE
C:\Program Files\Norton AntiVirus\navapsvc.exe
C:\Program Files\Norton AntiVirus\SAVScan.exe
C:\WINDOWS\Explorer.EXE
C:\Program Files\Common Files\Symantec Shared\SNDSrvc.exe
C:\Program Files\Analog Devices\SoundMAX\SMAgent.exe
C:\WINDOWS\System32\svchost.exe
C:\Program Files\Common Files\Symantec Shared\CCPD-LC\symlcsvc.exe
C:\WINDOWS\System32\Tablet.exe
C:\WINDOWS\system32\ZoneLabs\vsmon.exe
C:\WINDOWS\System32\wbem\wmiapsrv.exe
C:\WINDOWS\System32\dmadmin.exe
C:\Program Files\Analog Devices\SoundMAX\SMax4PNP.exe
C:\Program Files\Analog Devices\SoundMAX\Smax4.exe
C:\Program Files\Common Files\Symantec Shared\ccApp.exe
C:\WINDOWS\System32\PowerDesk8\Matrox.PowerDesk.PD eskNet.exe
C:\Program Files\LIUtilities\WinTasks\wintasks.exe
C:\Program Files\ASUS\Probe\AsusProb.exe
C:\PROGRA~1\ZONELA~1\ZONEAL~1\zlclient.exe
C:\Program Files\Adobe\Adobe Acrobat 6.0\Distillr\acrotray.exe
C:\Program Files\Coloreal\Coloreal Visual\Coloreal4Matrox.exe
C:\WINDOWS\system32\WTablet\TabUserW.exe
C:\Program Files\Messenger\msmsgs.exe
C:\Program Files\Lavasoft\Ad-aware 6\Ad-watch.exe
C:\WINDOWS\System32\WISPTIS.EXE
C:\Program Files\Internet Explorer\iexplore.exe
C:\Program Files\imagineLAN\RegSafe\regsafe.exe
C:\WINDOWS\Explorer.EXE
C:\Documents and Settings\Kyle\My Documents\My Downloads\merijn.org\HijackThis.exe

R1 - HKCU\Software\Microsoft\Internet Explorer\Main,Search Bar = http://www.google.com/ie
R1 - HKCU\Software\Microsoft\Internet Explorer\Main,Search Page = http://www.google.com
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,SearchAssistant = http://www.google.com/ie
R1 - HKCU\Software\Microsoft\Internet Explorer\SearchURL,(Default) = http://www.google.com/keyword/%s
O2 - BHO: (no name) - {06849E9F-C8D7-4D59-B87D-784B7D6BE0B3} - C:\Program Files\Adobe\Adobe Acrobat 6.0\Acrobat\ActiveX\AcroIEHelper.dll
O2 - BHO: Web assistant - {9ECB9560-04F9-4bbc-943D-298DDF1699E1} - C:\Program Files\Common Files\Symantec Shared\AdBlocking\NISShExt.dll
O2 - BHO: (no name) - {AA58ED58-01DD-4d91-8333-CF10577473F7} - c:\program files\google\googletoolbar2.dll
O2 - BHO: (no name) - {AE7CD045-E861-484f-8273-0445EE161910} - C:\Program Files\Adobe\Adobe Acrobat 6.0\Acrobat\AcroIEFavClient.dll
O2 - BHO: NAV Helper - {BDF3E430-B101-42AD-A544-FADC6B084872} - C:\Program Files\Norton AntiVirus\NavShExt.dll
O2 - BHO: inetLock route - {E02E86EB-220B-4B59-A251-F849405E1D64} - H:\Program Files\PC Magazine Password Profiler\inetLockBho.dll (file missing)
O3 - Toolbar: Adobe PDF - {47833539-D0C5-4125-9FA8-0819E2EAAC93} - C:\Program Files\Adobe\Adobe Acrobat 6.0\Acrobat\AcroIEFavClient.dll
O3 - Toolbar: Norton AntiVirus - {42CDD1BF-3FFB-4238-8AD1-7859DF00B1D6} - C:\Program Files\Norton AntiVirus\NavShExt.dll
O3 - Toolbar: &Radio - {8E718888-423F-11D2-876E-00A0C9082467} - C:\WINDOWS\System32\msdxm.ocx
O3 - Toolbar: Web assistant - {0B53EAC3-8D69-4b9e-9B19-A37C9A5676A7} - C:\Program Files\Common Files\Symantec Shared\AdBlocking\NISShExt.dll
O3 - Toolbar: &Google - {2318C2B1-4965-11d4-9B18-009027A5CD4F} - c:\program files\google\googletoolbar2.dll
O4 - HKLM\..\Run: [RegSafe] C:\Program Files\imagineLAN\RegSafe\ntfsclup.exe
O4 - HKLM\..\Run: [CfgRegSafe] C:\Program Files\imagineLAN\RegSafe\ntfsclup.exe
O4 - HKCU\..\Run: [MSMSGS] "C:\Program Files\Messenger\msmsgs.exe" /background
O4 - Global Startup: Coloreal Visual.lnk = ?
O4 - Global Startup: Image Transfer.lnk = ?
O8 - Extra context menu item: &Google Search - res://c:\program files\google\GoogleToolbar2.dll/cmsearch.html
O8 - Extra context menu item: Backward &Links - res://c:\program files\google\GoogleToolbar2.dll/cmbacklinks.html
O8 - Extra context menu item: Cac&hed Snapshot of Page - res://c:\program files\google\GoogleToolbar2.dll/cmcache.html
O8 - Extra context menu item: Si&milar Pages - res://c:\program files\google\GoogleToolbar2.dll/cmsimilar.html
O8 - Extra context menu item: Translate into English - res://c:\program files\google\GoogleToolbar2.dll/cmtrans.html
O9 - Extra 'Tools' menuitem: Windows Messenger (HKLM)
O16 - DPF: {41F17733-B041-4099-A042-B518BB6A408C} - http://a1408.g.akamai.net/7/1408/9955/20031016/akamai.info.apple.com/iTunes4/WW/win/061-0848.20031022.TtzS4/iTunesSetup.exe
O16 - DPF: {62475759-9E84-458E-A1AB-5D2C442ADFDE} - http://a1540.g.akamai.net/7/1540/52/20031028/qtinstall.info.apple.com/abarth/us/win/QuickTimeInstaller.exe
O17 - HKLM\System\CCS\Services\Tcpip\..\{9143A18F-0F68-4E69-B5E2-E639B82B0945}: NameServer = 205.152.144.252,205.152.0.5

BTW: Does anyone know about a process called WhiteRabbit?

--kyle

This is what I had for TCPCOM; installed is WinOff2003, and Wacom Tablet...--kyleIf I understand correctly you couldn't completely uninstall wisptis.exe? I suggest you try the 2nd method as mentioned here (http://www.turcic.com/forums/showpost.php?p=5610&postcount=18).

Never heard of a process called WhiteRabbit, but it doesn't sound so friendly ;) Do you have more info on it?

Btw, if someone has not yet removed wisptis from his/her system, could you please open your registry and look up all

HKEY_CLASSES_ROOT\TpcCom.*

subkeys and post the names for .* here? I have them already removed, but would like to know the keys so that I can also include them in the .inf script.Here are mine:
HKEY_CLASSES_ROOT\TpcCom.ClassicW.1
HKEY_CLASSES_ROOT\TpcCom.DrawAttrs
HKEY_CLASSES_ROOT\TpcCom.DrawAttrs.1
HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP
HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP.1
HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer
HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer.1
HKEY_CLASSES_ROOT\TpcCom.InkObject
HKEY_CLASSES_ROOT\TpcCom.InkObject.1
HKEY_CLASSES_ROOT\TpcCom.InkObjectXP
HKEY_CLASSES_ROOT\TpcCom.InkObjectXP.1
HKEY_CLASSES_ROOT\TpcCom.InkSettings.1
HKEY_CLASSES_ROOT\TpcCom.Lattice
HKEY_CLASSES_ROOT\TpcCom.Lattice.1
HKEY_CLASSES_ROOT\TpcCom.RecoManager
HKEY_CLASSES_ROOT\TpcCom.RecoManager.1
HKEY_CLASSES_ROOT\TpcCom.TabletManager
HKEY_CLASSES_ROOT\TpcCom.TabletManager.1
HKEY_CLASSES_ROOT\TpcCom.UserDictionary
HKEY_CLASSES_ROOT\TpcCom.UserDictionary.1

I have not yet uninstalled it and here are my TpcCom entries, I have office 2003 installed btw.

ClassicW
ClassicW.1
DrawAttrs
DrawAttrs.1
DrawAttrsXP
DrawAttrsXP.1
GenericRecognizer
GenericRecognizer.1
InkObject
InkObject.1
InkObjectXP
InkObjectXP.1
InkSettings
Lattice.1
RecoManager
RecoManager.1
TabletManager
TabletManager.1
UserDictionary
UserDictionary.1


Mat128
I hope it helps :P

Hello all,

I don't know, whether this thread is still alive, but here's my two cents:

I configured wisptis.exe in my Pop-up & Spyware blocker (AdsGone v5.0.1 build 16) as a spyware. Whenever wisptis.exe runs, my blocker kills it automatically. Prolem solved! ;)

Have a great time...

----------------------------------------
GT

Just a word of appreciation to those putting solutions to the above mentioned MS nightmare on this board.

I wish more of the Internet was filled with souls like you- especially for us tech challenged types...

I think Alex is including one section specifically for IT-related discussions like this one once his site update is done. Hope to see you onboard then!

There is a reason for running wisptis on a non-tablet pc. If you're running the ink api to send emails or msn messenger messages that include handwriting (or any kind of handdrawn image), you apparently need it.

Still, this isn't really "essential" functionality, so I understand those who want to get rid of it.

As an FYI, I am running Office XP and still have wisptis.exe on this Windows XP machine. I suspect this is not an Office 2003 issue, rather Windows XP.

FYI

WISPTIS.EXE is a parasitic program that can bring your browsing to a screeching halt.

Get rid of it! Visit Microsoft.com for info.

tr

Ouf!!!

Simply moving to adobe 5.1

For windows 2003 Server is:

HKEY_CLASSES_ROOT\Installer\Features\9040111900063 D11C8EF10054038389C

look for the WISPFiles and WISPHidden

not:

HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden


Also this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\9040111900063D11C8EF10054038389C

instead of this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden



Just a little helpful tip.

Thanks for this info!!!

Not to beat a dead horse.....
This thread is quite long and I'm sure everyone now has uninstalled/disabled wisptis.exe. But for me the quickest/easiest way was to simply locate wisptis.exe and then DENY myself read/execute priveleges. Seems to work for me.

eric

if you look up wisptis.exe on microsoft you can see that its related to microsoft journal viewer (AND NOT TO ACROBAT). uninstall journal viewer if you don't need it.

don't know how it pertains to office 2003

I followed the above instructions with success, but noticed a few changes that may affect some users...

HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden
January 6th, 2004

where the value is 7040110900063 D11C8EF10054038389C\WISPFiles, I found on my PC that it was 9040110900063 D11C8EF10054038389C\WISPFiles. This applies to all above listed keys where they start with 70, they appeared as 90.



(instruction also downloadable below)

The first time after I had installed Microsoft Office 2003, I noticed that whenever I run Adobe Acrobat Reader 6.0, a background process is started called wisptis.exe. Once wisptis.exe has been started, it won't stop unless you kill it or reboot your system.

In general, the ways in which wisptis.exe can get installed on your system:

installing Journal Viewer via Windows Update
installing Microsoft Office 2003

So what is wisptis.exe? A quote from TabletPCDeveloper.com:

Well I don't have a Tablet PC and I certainly don't want an unnecessary process eating up my memory resources.

You cannot get rid of wisptis.exe by renaming or deleting it: Windows File Protection would cause it to reinstall the next time you run Adobe Acrobat.

There is even a rumor about a bug in wisptis.exe itself whereby it keeps part of the current user registry hive locked, preventing updates and eventually resulting in a corruption of the registry hive (which as reported leads to a "Userenv event 1517" on logging off or shutting down).

Others reported GDI leaks and CPU hogging. I haven't noticed the latter but can confirm that at one point, the number of open GDI handles by wisptis.exe was above 1000, which is unacceptable.

So by and large it seems wisptis.exe can make a thorough nuisance of itself.

To uninstall wisptis and Microsoft's Tablet PC Components on your PC, you must delete the following registry entries:

HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}
HKEY_CLASSES_ROOT\AppID\wisptis.EXE
HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}
HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}
HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}
HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}
HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}
HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}
HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}
HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}
HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}
HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}
HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}
HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}
HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}
HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}
HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}
HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}
HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}
HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}
HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}
HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}
HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}
HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}
HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}
HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}
HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}
HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}
HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}
HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}
HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}
HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}

HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden

HKEY_CLASSES_ROOT\TpcCom.* (all of them)

HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}
HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}
HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}
HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden

Now you can also safely delete \Windows\System32\Wisptis.exe. Make sure the process is not running; otherwise kill it before deletion.

Fully tested on an up-to-date Windows XP SP1.

Cheers,
Alex

Thanks for the help all, appreciated.

Why are there 1001 places where code is executed at startup? To support administration and to avoid threats from weired programs there should be exactly one.

On a brand new system at work that was inexplicably slow and crashing and whatall. The advice on killing this thing is appreciated.

Just create a file on your desktop and name it "wisptis_remove.reg" (without the quotes of course), and cut and paste the following.

This is a reg file for WinXP.
If you have another OS, open regedit, export a selected key, delete all data that below the "Regedit4" (leave the blank lines), and then cut and paste the following (starting from the first "[-HKEY" line).

Ensure that there is no space above the first line in your .reg file, or you will get an error.

This will take the manual labor out of deleting all those darn keys.

Cheers,

Will

-----------------------Begin cut here-----------------------------

Windows Registry Editor Version 5.00



[-HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}]
[-HKEY_CLASSES_ROOT\AppID\wisptis.EXE]
[-HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}]
[-HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}]
[-HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}]
[-HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}]
[-HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}]
[-HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}]
[-HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}]
[-HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}]
[-HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}]
[-HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}]
[-HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}]
[-HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}]
[-HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}]
[-HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}]
[-HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}]
[-HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}]
[-HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}]
[-HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}]
[-HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}]
[-HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}]
[-HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}]
[-HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}]
[-HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}]
[-HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}]
[-HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}]
[-HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}]
[-HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}]
[-HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}]
[-HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}]
[-HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}]
[-HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B]
[-HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles]
[-HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden]

[-HKEY_CLASSES_ROOT\TpcCom.ClassicW]
[-HKEY_CLASSES_ROOT\TpcCom.ClassicW.1]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrs]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrs.1]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP.1]
[-HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer]
[-HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer.1]
[-HKEY_CLASSES_ROOT\TpcCom.InkObject]
[-HKEY_CLASSES_ROOT\TpcCom.InkObject.1]
[-HKEY_CLASSES_ROOT\TpcCom.InkObjectXP]
[-HKEY_CLASSES_ROOT\TpcCom.InkObjectXP.1]
[-HKEY_CLASSES_ROOT\TpcCom.InkSettings.1]
[-HKEY_CLASSES_ROOT\TpcCom.Lattice]
[-HKEY_CLASSES_ROOT\TpcCom.Lattice.1]
[-HKEY_CLASSES_ROOT\TpcCom.RecoManager]
[-HKEY_CLASSES_ROOT\TpcCom.RecoManager.1]
[-HKEY_CLASSES_ROOT\TpcCom.TabletManager]
[-HKEY_CLASSES_ROOT\TpcCom.TabletManager.1]
[-HKEY_CLASSES_ROOT\TpcCom.UserDictionary]
[-HKEY_CLASSES_ROOT\TpcCom.UserDictionary.1]

[-HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}]
[-HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}]
[-HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}]
[-HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827]]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden]

-------------------end cut here--------------------------------

P.S.

On the bottom of this reg file, make sure where it says "CurrentVersion", that there is no space between "Curr" and "ent" (i.e. Curr ent.
This happened because of the wordwrap in this input box, I think. Copy and Paste into notpad, uncheck wordwrap, and then check all lines to make sure they are not split (i.e. no spaces).


Thanks,

Will


Just create a file on your desktop and name it "wisptis_remove.reg" (without the quotes of course), and cut and paste the following.

This is a reg file for WinXP.
If you have another OS, open regedit, export a selected key, delete all data that below the "Regedit4" (leave the blank lines), and then cut and paste the following (starting from the first "[-HKEY" line).

Ensure that there is no space above the first line in your .reg file, or you will get an error.

This will take the manual labor out of deleting all those darn keys.

Cheers,

Will

-----------------------Begin cut here-----------------------------

Windows Registry Editor Version 5.00



[-HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034}]
[-HKEY_CLASSES_ROOT\AppID\wisptis.EXE]
[-HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424}]
[-HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA}]
[-HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC}]
[-HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4}]
[-HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB}]
[-HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C}]
[-HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB}]
[-HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C}]
[-HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F}]
[-HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D}]
[-HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C}]
[-HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137}]
[-HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026}]
[-HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73}]
[-HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3}]
[-HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83}]
[-HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9}]
[-HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3}]
[-HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255}]
[-HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B}]
[-HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF}]
[-HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1}]
[-HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29}]
[-HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576}]
[-HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5}]
[-HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE}]
[-HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4}]
[-HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8}]
[-HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F}]
[-HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586}]
[-HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B]
[-HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles]
[-HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden]

[-HKEY_CLASSES_ROOT\TpcCom.ClassicW]
[-HKEY_CLASSES_ROOT\TpcCom.ClassicW.1]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrs]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrs.1]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP]
[-HKEY_CLASSES_ROOT\TpcCom.DrawAttrsXP.1]
[-HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer]
[-HKEY_CLASSES_ROOT\TpcCom.GenericRecognizer.1]
[-HKEY_CLASSES_ROOT\TpcCom.InkObject]
[-HKEY_CLASSES_ROOT\TpcCom.InkObject.1]
[-HKEY_CLASSES_ROOT\TpcCom.InkObjectXP]
[-HKEY_CLASSES_ROOT\TpcCom.InkObjectXP.1]
[-HKEY_CLASSES_ROOT\TpcCom.InkSettings.1]
[-HKEY_CLASSES_ROOT\TpcCom.Lattice]
[-HKEY_CLASSES_ROOT\TpcCom.Lattice.1]
[-HKEY_CLASSES_ROOT\TpcCom.RecoManager]
[-HKEY_CLASSES_ROOT\TpcCom.RecoManager.1]
[-HKEY_CLASSES_ROOT\TpcCom.TabletManager]
[-HKEY_CLASSES_ROOT\TpcCom.TabletManager.1]
[-HKEY_CLASSES_ROOT\TpcCom.UserDictionary]
[-HKEY_CLASSES_ROOT\TpcCom.UserDictionary.1]

[-HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D}]
[-HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418}]
[-HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37}]
[-HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012}]

[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827]]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPFiles]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Featu res\WISPHidden]

-------------------end cut here--------------------------------

Lots of work to erase this file...

If it isn't necessary, what is it doing in my system? If it is why should I erase it?

I'm so confused :)

As you have constated with the different Product ID for the same product:
reverse the order of the bytes within each word of the sequence
(Big Indian Sex to Little Indian byte order)
That is for example C040 to get 040C for a french product,
9040 to get 0409 for an english product and as last example
7040110900063D11C8EF10054038389C to get 0407 a language that I
don't talk in my country..

To prevent the MS Tablet PC Ink Pen components to start up, I just unregistered them.

I created an XP batch file like this:

rem -- UnRegister MS XP Tablet PC Ink Pen components
set sys32=%SystemRoot%\System32
set pfcfink=%CommonProgramFiles%\Microsoft Shared\INK
"%sys32%\WispTis.exe" /unregserver
"%sys32%\regsvr32.exe" /u "%sys32%\inked.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%/inkobj.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%/inkdiv.dll"
"%sys32%\regsvr32.exe" /u "%pfcfink%/tpcps.dll"
set pfcfink=
set sys32=
pause

In my PC, the components were installed by the MS Visio 2003 Viewer. That program uses an MS Installer Database (MSI), so whenever I would "Repair" such an Office program, the Tablet components get reregistered again.
this script is great :)

Thank you for the scripts. Everything worked fine. No more Wisp

excellent work script -INF file- worked you should get a job removeing annoyances like that i am very greatfull for your help

thanks again
from me OmegaDVD a computer repair tech for 10 years(you still can teach an old dog new tricks)

OmegaDVD
HellStar Systems

thanks for the useful post.. should've looked down a few posts for the automated script :D

Wow, more than 74,000 views. This thread is gigantic! :dizzy2:

Ok here is a question.
I run the script and it does succeed in removing the .dll file from sys32... but so far as anything else from the script its a wash. As far as i can tell, I have no viruses yet my regedit cmd drops the registry explorer window as soon as it opens, and the task manager window also does the same. So at this point I cant even get to the file to disable it and run the remove scripts. As far as software, OS is XP Home, Office 2000 SR-1, and had Adobe Acrobat 5 with the Journal Viewer from the update but followed the instructions and uninstalled both to see if everything would work but a no go of yet.
Got any clues?

Thanks.

If I understood you right, you cannot start the command prompt (CMD) now? It is difficult to tell what causes this, especially since I don't know what process run in the background of your Windows. Could you download Sysinternal's free Process Explorer (http://www.sysinternals.com/ntw2k/freeware/procexp.shtml), save the information as .txt and post them here? It would help if you register, because then you can attach .txt files.

Alex

Ok got the info you needed. The activity in question was that I could not open the regedit nor the task manager because they would both close almost as soon as they opened. The short cut for the dos command prompt would not work but the run command from the start menu tab would work. But that was secondary on my concern list as I had wanted to access the task manager, but would get bumped every time. The program link was nice though. I got the process explorer and can go into the system process now. This is the txt file from that.
Sorry to be abrupt, but I must head to school now but will check the results later tonight.
Thanks for the help.
Its much appreciated.

Jae

Ok, I couldn't find anything particular wrong with the processes on your machine.

However, I suggest you remove the MDM.EXE Machine Debug Manager, which you probably won't need and which was reported to cause problems: http://support.microsoft.com/default.aspx?scid=kb;EN-US;321410

Also, try to remove or at least stop the CTFMON.EXE process. Another process that most people don't need and that is bug-fested: http://support.microsoft.com/default.aspx?scid=kb;EN-US;282599

I assume the Silitek processes are part of the drivers of a USB keyboard or something like that. So that's fine.

Does the Taskmanager start when you enter 'taskmgr' in the command prompt? Perhaps you should try to disable some services like the Symantec Virus checker and see if it makes any difference.

Greets
Alex

Find the stupid file and take away the execute permission from all the users. It's not as thorough as a full reg flush but a heck of a lot easier and safer.

And I'm all for lazy, I mean easy.

If you don't know how to mess with the permissions, well, I'm too lazy to write it.

Cheers

Saben

Uninstall the Microsoft Windows Journal Viewer (It is one of the Windows Updates, but it is listed in your Add/Remove Programs list). (snip).

I just tried to remove Windows Journal Viewer, but am told that I do not have the right to do so. Help?
(Win 2K, single user, and I log in as administrator)

(Sorry if this is a stupid question)

Instead of removing the Journal Viewer, have you tried to only run this script:

http://www.mobileread.com/forums/showpost.php?p=5595&postcount=14

A more general solution to problems like this is to use windows file security to lock down the offending file.

I have also used this in one job when some fool in IT insisted that we have some garbage "management" software on our systems. You'd kill the processes, remove the directory, and next login it was back, worse than a virus.

Right click on the file / folder in question, select properties, and hit up the security tab. This tab isn't present by default on XP Home, yet another classic MS bugger up. Go to http://www.tweakxp.com/displayf.aspx?id=11654 and follow instructions to get this tab to show.

Uncheck the "allow inheritable permissions" checkbox, and then for all users / groups shown, deny everything. For good measure, I add an entry for "Everyone" and deny all on that. Hit OK, the system will bitch at you that you've prevented everyone from accessing the file (duh!), tell it that it's OK, and you're hot to go.

** Seems like in my system the mentioned keys starting w/ "7040..." were "9040...", so please verify your systems.

But the solutions you guys found are fantastic!!!

You guys Rock

This thread was viewed over 90'000 times!!!Incredible... so many people are annoying by one little MS process ;)

This thread was viewed over 90'000 times!!!Incredible... so many people are annoying by one little MS process ;)
Wish you could make that into 90'000 posts ;) Patience, Alex, patience...

Thanks alex for putting together that inf...

All you geniuses couldnt figure out the simple way to kill it :) Go to C:\windows\system32 and rename wisptis.exe to wisptis.bak. Then create a new empty text file in the same location. Name the text file wisptis.exe.

This means that any time something tries to run wisptis.exe it'll actually execute a 0 byte text file. Notepad wont actually open, and no unwanted programs will remain running, so dont worry about that.

Benefit 1: if you actually find you do need wisptis.exe (if you decide to buy a palmtop or whatever) all youve got to do is rename wisptis.bak to wisptis.exe again.

Benefit 2: you dont need to mess with your registry, and you dont need to run files that do it for you (you may not trust a file from a complete stranger when its deleting parts of your registry).

Benefit 3: Things change. In the next acrobat/microsoft office/etc the registry keys may change location. This means youll need a new file to modify your registry depending on what versions of this crap youve got installed. My method should work no matter what versions youre running.

Side note 1: I have no idea if windows file protection / system restore will attempt to fix it on some computers. I turn most of that garbage off, but file protection is on and caused me no problems.

Side note 2: make sure youve got "show extensions for known file types" turned on, or youll have accidentally have created wisptis.exe.txt instead, and that wont work.

Side note 3: you must create the empty text file. Deleting or renaming wisptis.exe alone will make things try to reinstall themselves when you run them.

Dont try to contact me, i'll likely forget that i posted this here. So no, i can't offer tech support. Feel free to put this advice on any forum you like and share it however you like, but give me (Mark W) the credit for the info.

... there is nothing new about your suggestiong; in fact it was already suggested on page 2 of this thread:
http://www.mobileread.com/forums/showthread.php?t=1260&page=2

The catch is though even if you create an empty text file, Wisptis is likely to return the next time you run Adobe Acrobat, either because of Windows File Protection (WFP) or because of Windows' prefetch mechanism. And I would strongly recommend AGAINST turning off either of the two features.

I just registered here.. looks like an excellent forum :).

I love the forum script.. looks very good, and the features are sweet :). The site is also extraordinarily fast to navigate, seems like this is on some good hosting :)

Anyway, I read the whole thread, but there have been so many suggestions and counter-suggestions and additions and different methods that all reading the whole thread did is to confuse me. What is the ultimate solution to getting rid of wisptis.exe now?
Thanks in advance :)

Welcome onboard MoeRL! Glad you enjoy it here ;)

I come back to you in a couple of hours, when I have some more time!

Cheers

Welcome onboard MoeRL! Glad you enjoy it here ;)

I come back to you in a couple of hours, when I have some more time!

Cheers

I appreciate the quick update :). See ya then, take your time.

Dammit.. sorry, that was me. Forgot to log in :(

I have the page "cookied" in Opera, but now I'm here with FireFox and forgot I hadn't logged in before with FF :). Here we go :)

If you have MS Front Page 2003

Open "add/remove programs", select "MS Front Page 2003" and click "change" button. Now chose "Add or Remove Features" and click next , there expand "Office Shared Features" and click on "Microsoft Handwriting Component" and select "Not available" and click "update". If that's no help then expand in the same tree "Alternative User Input" and do the same for "Handwriting" option. I can't now remember which is one of that two guilty because I have them both uninstalled. After this there is no more that WISPTIS.EXE and MS installer.

What if I don't have Frontpage? Which I don't? I have MS Office 2003.. Word, Excel, Powerpoint, Outlook, all installed.. but I don't need FrontPage so it's not installed. Any other way/

MoeRL, try what the previous poster said with your Office installation. See if you can also find the Handwriting Component and try to disable it.

I am sure one of the registry methods mentioned earlier in this thread works, but using the method described here just before would be the "cleaner" solution.

Yeah, this stupid process (Wisptis.exe) is using up 9999 GDI objects and is preventing me from opening any other programs.

MS really needs to work on preventing resource leaks...

In the meantime, I'm going to uninstall the Journal Viewer...

I thought just a tad further and thought I'd give you this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;823586&Product=off2003


:)

Whoa.. check it:

This article describes how to turn off speech recognition and handwriting recognition.

Microsoft Office contains a speech recognition feature and a handwriting recognition feature. You can use speech recognition to dictate text to any Office program. You can also use your voice to select menu items, toolbar items, dialog box items, and task pane items. (You can use your voice to select dialog box items and task pane items only in U.S. English language versions of Office.) Speech recognition is installed as part of a Typical or Complete installation of Office. If you perform a Custom installation, Office Setup installs the features as part of the Alternative User Input feature in the Office Shared Components.

You can use handwriting recognition to type text in any Microsoft Office program by writing instead of typing. You can write by using a mouse or by using a third-party handwriting input device. Office programs can automatically convert this input to typed text. In Microsoft Word and Microsoft Outlook (if Word is your e-mail editor), the input can be left as an "ink object" in your own handwriting. Handwriting recognition also supports a drawing function, so that you can include hand-drawn sketches in your Word document.

After you install Office and then you turn on speech recognition and handwriting recognition, these features become part of the operating system. You cannot remove these features, even with the Maintenance Mode of Office Setup.

But of course, with the method described on that page, it can be done :)

I just wanted to say thanks for the script. Worked well on my XP Pro OS and solved the annoying problem WISPTIS caused with my tablet.

Sorry but this solution does NOT work.

I FOUND IT RUNNING AFTER I INSTALLED MSN 7 BETA,AND I HAVEN'T NOTICED IT BEFORE.

HOW SHOULD IT UNISTALLED IN THIS CASE?

I JUST SEARCH IT AND GET ONE .PF FILE DELETED.

This is for all you guys who first checks the end of the thread: here's a summmary referring the best posts.

- First of all this problem applies to all NT versions as well, like Windows 2000 and Windows 2000 Pro

- Every type of solution possible is posted at least twice, and often discussed endlessly

- As usual in a long thread(98 posts/7 pages before me!) some people don't bother to read it through anymore,
in stead they add their own 'unique' solution. Post #85/page 6 is a hilarious example: he really thinks he's the first
with that solution, while in reality, the very same solution is described in posts #21/page 2(!) and #38/page 3...
Still, the arguments for this solution put forward in post #85/page 6 are excellent. Read them and ponder.

1. Solution type 1: *RECOMMENDED*
Represented by post #85/page 6, which has an excellent summary of the arguments for this kind of solution.
Post #53/page 4 also points out what so many seem to forget: that there might actually be situations where
you need to load he wisptis.exe, even on a non-tablet pc because it interacts with the mouse as well...
(see post #1/Page 1!), and with this solution it's done in a breeze.

2. Solution type 2: A good alternative, effectively the same as solution type 1
The general idea is to keep the wisptis.exe from loading without messing with uninstalls/registry hacks,
which is exactly what solution type 1 does(read post #85/page 6 if you don't understand why this is the best approach).
However there are countless other ways of achieving that, and this solution type is probably a more widely useful
approach: the zero bite file in solution type 1 did after all require some specialized know-how.
Represented by posts #50/page 4(splendid thinking), #80/page 6(a bit messy though).
I'm sure that many of you can come up with a couple of more ways, but PLEASE, don't add them here!
We all get the hang of it...

3. Solution type 3: The DIY-home carpentry solutions including all kinds of uninstalls/registry hacks
If you don't get by now why this is *NOT* the recommended way to go, I'm not gonna try and stop you.
You just go right ahead and try whatever fits your personal taste.
Though I do suspect that you really have to much time to kill(like me writing this post - phew :) )

Conclusion
----------
This thread was viewed over 90'000 times by thread #82/page 6, and now it's exactly 115,687...
Even if people surely will keep reading it, I hope you all agree that what we DON'T need is more of these
'great job' comments or DIY-home carpentry solutions, like endless registry key references
(they never have, and never will, always be exactly the same for all versions of Windows - OR Office - go figure if U
really think that's the way to go when you're advising EVERYONE to do it your way when there ARE controlled ways of
fixing this problem - I KNOW it worked for you, but that does NOT mean that it's a great idea to post it here...). :(

PS. There are also a couple of nice tips about tools in this post, but I'm not gonna spoil all your fun finding it
yourselves :) - but I could mention that there is a reference to a tool that disables almost all of the useless
plug-ins that come with Acrobat Reader 6 - so you dont have do downgrade...
DS.

So, in hopes that this is - the last - post regarding how to actually fix THIS problem...

Bye, bye

This works on win2k. Edit to fit your Windows directory structure. Save to "Disable-Enable wisptis.exe.vbs". Pls note U must first create the zero byte file (wisptis.exe.zero)


'Disable-Enable wisptis.exe

'--------------------------------------------------------------------------------
' Written by ProgrammerDude
'--------------------------------------------------------------------------------

subject ="Pen input device"
pdir ="C:\winnt\system32\"
pgm ="wisptis.exe"
Set fso = CreateObject("Scripting.FileSystemObject")
If Not fso.FileExists(pdir +pgm +".disabled") Then
Set file = fso.GetFile(pdir +pgm)
file.Name = pgm +".disabled"
Set file = fso.GetFile(pdir +pgm +".zero")
file.Name = pgm
MsgBox subject +" has been disabled." _
, vbExclamation +vbSystemModal, " " +subject +" has been disabled"
Else
On Error Resume Next
Set file = fso.GetFile(pdir +pgm)
file.Name = pgm +".zero"
On Error Goto 0
Set file = fso.GetFile(pdir +pgm +".disabled")
file.Name = pgm
MsgBox subject +" is enabled." _
, vbInformation +vbSystemModal, " " +subject +" is enabled"
End If