Windows 7: Waiting For Background Process(es) To Close

You might temporarily disable that startup item to see if it still happens.

well, atleast i know i'm not alone and its just my lonely one world crazy pc configuration setup.... the conspiracy theory

its a bugger Brit, and tbh i havent gotten around to sussing it just yet, I just try to not reboot as much as possible, hehe... sad but... maybe try an upgrade ti 27, with a backup? I'm about to wipe 7100 off and start a new with the 27, and probably, foregoing any catastrophes and stick with it, as it seems pretty stable as compared to the 7000 imo.

just to add some worthy info... i have a lexmark and a kodak on the network, but i dont think that is it, could be, but my nugget tells me its something simpler than that even. I want to blame a gadget, but i dont think i can, yet anyways, tho it could be that or something as trivial as such. I've been down the list of startup, repairing startup, so on and so on. no good. and thats about my length of dedicated time to it, just decided to not reboot unless needed, which isnt a big deal anywho for me.

LOL. Some parts of Windows & its inner workings will always remain a mystery to me. They simply defy logic.
Anyway, it's still disabled and I've rebooted 6 times. The last boot started up with a popup Windows Image Aquisition has stopped working, send error report? So I did.
Maybe it had something to do with that.

That taskhost thingy still appears momentarily at shutdown, but there isn't anything in it, as far as I can tell, as it's literally only up for a split second. Another annoyance, to me if Windows wants to tell you something, for Gawd's sake let me read the damn thing.

Back to the drawing board, or should I say grindstone.

hahaha... i hear ya Brit... i had this EXACT same thought the other day....

Well I'm going to re-enable that darned thing, just in case. Who knows, I may be causing a landslide somewhere in Asia by turning it off.

I was having a curious problem with Win 7 message stating "Waiting For Background Process(es) To Close ". I did all the normal techie things like, disabling startup processes one by one, changing shutdown settings (Wait To Kill Timeout) etc. Then when I went to fix a printing problem on a Lexmark wireless downstairs, I discovered the AC plug had been unplugged. When the printer reconnected to my network I later noticed that my "Waiting For Background Process(es) To Close " issue had not re-occured. Shazzam, since Windows 7 wasn't getting a disconnect message from the unplugged printer, it must've been re-trying to confirm log-off, thus slowing shut-down. Go figure.

Thnx Ex_Brit. I stumble dupon this thread juz now, otherwise would have started a new thread with this same issue. From the usage of Win 7, I was also bugged upon this issue till now. Here is my case,
I have 2 heavy applications always open during daytime. Outlook and FF. Before shutdown or restart, I close them, but FF takes some time to close. At this moment I get the same above message but it will nt list wat process is running. Strange. What I do is, click on force restart and then click on yes.

Sometimes if my explorer is opened, I get it listed. Sometimes for Outlook too. But strangely, eventhough there are no applications open, I get this screen and message by default.

When goin thru the above post, I was thinking whether the network printer I have connected to my lappy is causing the problem. Because, back in home I havent seen this screen. Also a extra note, I am connected in a Domain.

I have to do that same forced shut down sometimes. Not always....weird. Event Viewer may have clues, haven't really had time to check.