Timeout Delay at Desktop on Startup

[TVeblen]

Short Explanation:
My Canon MF3240 laser printer is causing a timeout delay in W7, when completing the loading of the desktop when booting (cold or warm).

Long Explanation:
When starting the computer, Windows will load normally to the desktop with near complete functionality. But there is a delay of 60 seconds while something tries to initialize or load. During this delay the blue spinning circle ("Working") can be seen over the Network icon in the systray, and over the Currency & Weather gadgets, and in Windows Explorer at the major headings.

While the "Working" icon is showing I can open the browser and I have internet access. But I can't open task manager or use Windows Explorer until "Working" is done.

The condition was first noticed after I uninstalled my old Canon MP780 printer and replaced it with an Epson Artisan 810. The Canon MF3240 was already installed before this change. I always suspected the Epson printer had corrupted something. This weekend I finally got around to removing all the printers, cleaning up, and reinstalling the printers.

I reinstalled the Epson first (using correct W7x64 drivers) and all was good. Windows boots right up onto the desktop and everything is connected - no delays.

Then I reinstalled the MF3240. Bang - right off - the delay condition.

Now, if I unplug the USB cable for the MF3240 and boot (cold or warm) the delay goes away.

What do you think is going on here?

More Info:
The original installation of the MF3240 was done when I first installed W7. I was new to W7 and there was some thrashing about to get the printer set up, I recall. I finally got it working by manually installing the drivers. These were XP-2000 drivers, best I can tell.

The driver I just installed for the MF3240 is MF3200_MFDrivers_Win_x64_us_EN_7 .
I got these drivers from the Canon website for my printer, but I can't remember exactly when, but it was a while ago. I never installed these drivers before.

Today, on that website, the only W7 driver available is MF3200_MFDrivers_Win_x32_us_EN_7.exe ".
Actually, that is the only driver for all Windows OS's.

Also, the downloads above do not contain an installer package, only the .inf's and .cab's.
If I knew then what I know now, I would plug in the printer, Windows would not find a driver, I will browse to the folder with the drivers, and the x64 drivers are installed.

On the reinstall Windows found drivers and installed them automatically when I plugged the printer in. I had to go to the printer's properties and update the drivers to the x64 version.

However, the delay condition happens in either version of the driver that I had installed.

 

[Bare Foot Kid]

Hello TVeblen.





Have you had a look in the startup file in msconfig to see what may be having issues when you start the PC?


Troubleshooting with MSCONFIG

 

[TVeblen]

Good Tip BareFoot

I disabled the Epson EEventManager Application item and rebooted (warm) with the laser plugged in - no delay. I will run it a while like this a while to see if there are any repercussions with the Epson printer.

Anyone know what EEventManager does?
I can uninstall it from Control Panel > Programs

 

[Bare Foot Kid]

Glad it seems to be sorted, thanks for the update and keep us informed; I have no idea what that may be/do but keep checking back as someone may have some info on it for you.

 

[Petey7]

All I know is that it is part of the scanner software. It's needed to scan when ever you want by just pressing a button on the printer. It is my understanding that it opens other Epson software as needed when you scan something. Without it running, some software may have to be started manually.

I haven't owned an Epson printer so I'm not sure. I worked on a computer that had one connected and looked up this info before. I recommend testing everything I just said to see if it is valid or not.

 

[TVeblen]

Yes, after looking into it the EEventManager Application can be started manually anytime you need it. There is no effect on the functions of the printer when this app is not started automatically. Just another bloatware nuisance.

I'm off to edit my registry!