Wisptis.exe - How to get rid of another Microsoft annoyance

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

[Alexander Turcic]

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.

[formax]

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++

Originally Posted by formax

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?

Originally Posted by Beamer

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!

Originally Posted by sUnShInE

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.

[Alexander Turcic]

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.

[Alexander Turcic]

Originally Posted by Buz

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, which was reported to me to work fine.

Alex

Originally Posted by SecureUser

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

Worked for me. Thanks.