Software Deployment

These responses are dated 2005..?? I recently got this HKCR\CLSID\ showing up in my McAfee scan (7/30/2016). So who are you or what is it. I am 64 bit and it should not be wanting my system. Whoever knows who or why this thing is popping up... send me a message. The shortest way is to report this thing to the NYS Attorney General. But it may be an innocent old loop. It took McAfee  almost six hours to scan it with zero results. But I don't need it and don't want a stranger in my system. 

Although it's possible that things will still work without a particular threading model being specified for the server, I would prefer to assume that it has been specified for a reason.

Deleting the entry from he registry table will mean that the entry probably won't be written to the registry unless a selfreg table entry exists to do the registration instead.

Hi WiseUSer,
Thanks for ur Reply, But when we have these registry entries(InProcServer32\Threading Model) in COM Registration(CLASS Table of MSI) why are they not getting created in some cases in Registry?????
Do You mean that the application will not Function Properly if we delete these InProcserver32 registry entries in Registry Table of MSI(As these are present in COM registration).

What Exactly are these InProcServer32 registry Entries, What are there Specific Functionality?????

Thanks
Dev

I never touch registerfiles inside HKCR. I always keep these intact and I never experienced any problem with it.

I think it takes alot more time to sort them out that what you get out of it.

The "Class" table should create the "InProcServer32", but I'm not sure that it will ever create the registry key that specifies the threading model? I know that the SDK refers to "the path to a 32-bit in-process server and the threading model" when defining the "Context" column of the "Class" table, but I've never seen the threading model specified here.

The InProcServer(32) and LocalServer(32) provide the path to the "server" (dll, ocx or exe) for the component. When these entries are created through the MSI "Class" table, an extra entry is created which represents an advertised entry point to the MSI installation. This entry point is only used by shells that are advertising-aware, OS versions prior to NT4 (and early NT4 SP levels) will use the default (readable) path to the component.

I would recommend that you leave these registry entries as they are unless you have a specific reason to modify/remove them?