wisptis.exe

Hi All,

Can anyone tell me anything about wisptis.exe, I googled it ... and I'm no further ahead!

Thanks

Steve

 

here is one explanation

 

Thanks BigC

When I googled it ... all I could find was ... pen recognition for Tablet XP ... which left me more as both are n/a to me. Now the mouse on the other hand ... makes more sense. So the questions is ... Why can't Microsoft write anything in the English that we speak?

Thanks

Steve -

 

then we wouldn't have to pay for support if we could understand what the heck they were trying to say.

 

go to http://support.microsoft.com/default.aspx?scid=kb;en-us;821223&Product=winxp

PRB: Problems When Hosting Tablet PC Ink Collection and Managed Objects in Internet Explorer
View products that this article applies to.
SYMPTOMS
When you try to use the Microsoft Windows XP Tablet PC operating system ink collection and managed objects in a Windows Form (WinForm) or in an ActiveX control that is hosted in Internet Explorer, you may experience the following symptoms::

* Security permissions related problems
* Unexpected inking behavior: ink may not flow from the tip of the pen as expected
* Closing modeless dialog boxes: you may lose inking capabilities after you close modeless dialog boxes

CAUSE

* Security Permissions Related Problems
The security model in Internet Explorer does not allow unmanaged code to be executed without first modifying the security permissions under which it can run. Because the Microsoft.ink.dll file includes unmanaged code, it is bound by the restrictions of the default Internet Explorer security permissions.
* Unexpected Inking Behavior
In some instances (such as modal dialog boxes), the Pen Input Service (WispTis.exe) might not be informed of changes in the position of a window. When this occurs, the ink appears to flow from a position that is not directly under the tip of the pen.
* Closing Modeless Dialog Boxes
The Pen Input Service (WispTis.exe) object cache and the client application object cache become out of synch. When synchronization does not succeed, inking functionality in the hosted ink controls is also affected .

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. Microsoft is currently investigating a resolution.

 

THE solution is "easy"

Information from http://www.turcic.com by Alexander Turcic

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\BCA32ECD550E1F4488DBD2A1578ACF8B
HKEY_CLASSES_ROOT\Installer\Features\7040110900063D11C8EF10054038389C\WISPFiles
HKEY_CLASSES_ROOT\Installer\Features\7040110900063D11C8EF10054038389C\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\CurrentVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62580BE1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52DE68CA4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CDE3BF4D
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA34E827
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Features\WISPFiles
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038389C\Features\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.

very easy waht you think?

 

i think there is a more simple to get rid of running wisptis.
just run it once with -unregserver command line parameter.
%SystemRoot%\system32\wisptis.exe -unregserver
this will not terminate currently running wisptis, but will
prevent it from further starts. it shall also remove
(some of) those registry entries mentioned above.

 

hey darkelf...thanks for the command...this process always seems to creep back in eventually, probably due to me uninstalling/reinstalling Adobe and Office 2k3 all the time while troubleshooting issues with it for users; atleast initially, after running that command posted above, when I launch Outlook (which i'm thinking is calling the wisptis.exe process thread within Explorer shell) I only get my editor (winword.exe) which I feel is acceptable. The starting of a process for a Tablet PC when I have zero operations with Tablet PC, in any way, is totally unacceptable and flat-out annoying. Adobe and Microsoft should stop causing this bloat process to come up by default. You'd think Microsoft, a company in so much heat for exactly this kind of shameless and unnecessary promotion of their proprietary software, would not be so foolish as to be launching a process and taking up CPU for something most people don't and will likely never use...to have it launching by default...to me this is no worse than the stupid spyware/adware stuff we see in the wild these days.

I highly recommend this app, especially for this kind of junk:

http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

...also the tcp monitor offered for free on this same site is superb, here's to Sysinternals for doing a service for the people!

 

Well they are all in bed together , processor people, hardrive people, memory people, BLOAT WARE WRITING PEople, its whats makes them all richer.

Scenero: (BILL G) Say If we Write Bloat code... you Allen (AMD) and you IVan (Intel) make faster chips, and you Mark(Memory Maker) can sell More Memory, and you Harry Dick and MOe ( Hard Drive Maker ) Sell more Space .

And we at GIANT SOFT can Roll Out **** Code Faster .

Now Where is My ****in Kick Back !!!


BILL G

 

This process starts up when you launch MS Office or Adobe Acrobat. But when you close those programs, it continues to run in the background.

Also, if you add the "GDI Objects" column to your process list, you can see that it slowly leaks GDI objects, until it finally hits the max of 9,999. At that point, your computer locks up because none of your other applications can draw anything on the screen.