Need Help Blocking CONIME From Being Inserted To STARTUP

[UserA789]

I have a Kodak printer. They CANNOT understand that even MSFT has pretty much abandoned the 'conime' protocols, as the maker of BFGHOST owns that sh#t at this point in the game, and bravo to his perfection of scripting.

I am trying to put together a script file for Windows 7 to prevent this file from being constantly re-added to my start up files.  I don't even have CONIME on my system so it becomes a matter of resource hogging for my machine to be forced to try and locate it, let alone try and initiate a file that does not exist.

My efforts are all in dBase V1 and windows don't always like it and causes more conflict than Im ready to hunt down.

Can someone present a script and where to 'register' it to prevent Kodak from re-inserting 'conime' into my startup list.

[CraigB]

Have you tried looking in services as you might be able to stop it there or even the CCleaner startups might list some of the Kodak processes which you can disable.

[bob3160]

Another place to look is MSConfig  and if you're using Winpatrol, check out it's startup section.

[UserA789]

Have tried both of those.  I use another Utility to disable it when it gets re-inserted by Kodak trying to update.  You can no longer dsable UPDATE on the Kodak software either.  There also is no service to go fully disable (unless someone knows otherwise) that wont also interfere with communication from/to the printer.

So I can disable it... it gets re-inserted.

I can delete the entry... same thing.

There is no 'conime' file on Windows 7 (SP1)... at least mine, nor has there ever been.  So Im more concerned about system resources point of view.  But, as I said, ever since BFGhost took over the conime file MSFT pretty much started looking elsewhere for international character coding.

[mchain]

hi UserA789,

You can check your file here:  http://systemexplorer.net/file-database

• http://systemexplorer.net/file-database/file/conime-exe/5933
• http://systemexplorer.net/file-database/file/conime-exe/1370127
• http://systemexplorer.net/file-database/file/conime-exe

XP, Win 7, Vista, in that order.  However, Win 7 file is not from Microsoft.

[bob3160]

There is also more information about conime.exe available directly from Microsoft:
http://answers.microsoft.com/en-us/windows/forum/windows_vista-files/conimeexe-what-is/1c6eaa96-479b-4026-83d6-a2bced9d5dcd

[UserA789]

There is also more information about conime.exe available directly from Microsoft:
http://answers.microsoft.com/en-us/windows/forum/windows_vista-files/conimeexe-what-is/1c6eaa96-479b-4026-83d6-a2bced9d5dcd

Iv been there Bob.  Thanks tho.

This is really a Kodak issue, as it will not let me choose manual or auto update any longer.  When they made this change, the 'conime.exe' startup entry started to re-occur.  It was not an issue before this.  While I state that BFGHOST owns conime at this point; I do noit think I am his latest victim.

Just a victim of #Kodak choosing to disregard others safety just for user friendliness and not wanting to take calls when an update is all the fix needed.

As the owner of my printer and PC I should have the ability to not have something not even on my system at all forced into start up.  It's a simple matter of system resource as Kodak gets my PC looking for a file that has never existed on it (even after new installation).

[mchain]

There is also more information about conime.exe available directly from Microsoft:
http://answers.microsoft.com/en-us/windows/forum/windows_vista-files/conimeexe-what-is/1c6eaa96-479b-4026-83d6-a2bced9d5dcd

Iv been there Bob.  Thanks tho.

This is really a Kodak issue, as it will not let me choose manual or auto update any longer.  When they made this change, the 'conime.exe' startup entry started to re-occur.  It was not an issue before this.  While I state that BFGHOST owns conime at this point; I do noit think I am his latest victim.

Just a victim of #Kodak choosing to disregard others safety just for user friendliness and not wanting to take calls when an update is all the fix needed.

As the owner of my printer and PC I should have the ability to not have something not even on my system at all forced into start up.  It's a simple matter of system resource as Kodak gets my PC looking for a file that has never existed on it (even after new installation).

That's always been the case with obsolete and thus unsupported software from any vendor.  It's not supported anymore, and therefore no fixes will come in now or in the future. 

What do you think is the solution?

[EDIT:]  One solution that works is to rename offending file to .old, so it does not run anymore.

[UserA789]

What do you think is the solution? To ask someone smart on the Avast! forums help in writing a startup script that either disables the startup entry or deletes it; probably the first option.  However; as the elow picture shows its not easy to stop
[EDIT:]  One solution that works is to rename offending file to .old, so it does not run anymore.

There is no file to rename.  The problem is NOT Microsoft; the problem is #Kodak trying to implement unsupported/un-used software/protocols because they are lazy developers. The startup entry can be disabled or removed; but you will see from the screenshot Kodak gets rather annoying with it.

I traced it to the Kodak AIO Software package and updater.  The used to give us the option to disable automatic updates and as long as I disabled Services to FB, Picasa, and a few other social sites I would never see this startup entry.  Now, without the option of disabling auto-updates I cant stop it even with disabling the Kodak sharing services as before.  So updating is the culprit by process of elimination(s).

You cant even get an offline installer for their suite... Im getting WAAAY tired of that BS excuse to provide "better end user friendliness" and getting the proper updated CD meida is worse than trying to cancel your AOL subscription!!!

OFF TOPIC:  What, does BFGHOST work for Kodak?

[CraigB]

Are you able to go into the Kodak folder and delete the update.exe file or whatever it may be called, kill the process at the root.

[UserA789]

Are you able to go into the Kodak folder and delete the update.exe file or whatever it may be called, kill the process at the root.

I'll give this a temporary try.  I think I might hit some printer forums to see if anyone knows something I can adjust in the "KodakAiOUpdater.exe.config" file; or elsewhere if its some other persistent service.  Doing what you suggest will further eliminate other causes.  It is only after the Kodak AIO is installed though so I knew where to start.

Thanks.

[UserA789]

Are you able to go into the Kodak folder and delete the update.exe file or whatever it may be called, kill the process at the root.

So far renaming the file has prevented the start up entry.  Still looking for help to deal with the config file so I can still update.  The toold updates FW and SW so I want my printers FW to be kept up do date.

[CraigB]

How old is the printer ? more than a couple of years and you can forget about getting firmware updates.

[mchain]

Glad that renaming worked for you.

However, without the name of the updater program, as there can be several versions, and/or specific version as well, hard to tell if this is really an issue of old, obsolete software or something that is currently supported by Kodak.

Old, unsupported software can be the root cause of exploitation and an entry point of systems by malware authors.

[UserA789]

Old, unsupported software can be the root cause of exploitation and an entry point of systems by malware authors.

I agree but this software isn't even on my machine; just a start up call for the software.  The whole All-In-One install was updated two months ago, the FW on the printer earlier this year I believe.  I just don't get why some tech's are waaay lazier than should ever be allowed.  I get the file may be necessary if someone still runs XP or Vista (which DO have the file conime), but I don't think its been a part of MSFT's releases since Windows 7... maybe Win7 SP1.  I'm not sure how easy it would be to exploit the file call itself; when there is no file.

I was more getting rid of something that Windows might bottleneck searching for.