I have Windows 7 64 bit Ultimate SP1. When I click print in Office 2010 or in itunes the app instantly goes unresponsive and I often have to reboot pc it is so hosed. I have reinstalled office and itunes and I have reinstalled my printer with no effect. I can pront fine with notepad, wordpad or mspaint. I have no errors in any of the event queues. I have run uniblue registry check as well as the microsoft fixit. There are no virus or mal ware reported by Kespersky. I dont think it is an issue with the spooler or printer as the printer dialog doesnt even come up that would allow me to select to print to a file. I have even removed all printers so that print to file would be the only option. I have tried bypassing the spooler by selecting print directly to the pronter. When I click on the pront option in office (word, outlook, power point etc) instead of having the pront dialog popup to chose a printer, the app instantly goes non responsive. If I am able to close the app all I see in the event queues is a mention of an app stalling, nothing previous. I have tried to reload windows but when I try to unload SP1 so I can run setup (my org disk is pre SP1) the unload hangs at 44% and never completes. I can't run reload since my disk isn't SP1 and says I have a newer version I'm trying to update from. I have backups but none that predate the problem. This is my main platform for the family so there are many accounts and lots of applications. It will be very messy to do a clean install. Does anyone have any ideas.

Hi, Base on my understanding, Windows 7 will hang when you print office, but it works will when print other files. I suggest to logon with Clean Boot to exclude some third party services and programs. In addition, temporary disable antivirus and UAC on Windows 7. Also make sure the printer driver is support to Windows 7. Furthermore, you can try to create another administrator account and login to see if the same issue occurs. Hope that helps. Regards, Leo HuangPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Base on my understanding, Windows 7 will hang when you print office, but it works will when print other files. I suggest to logon with Clean Boot to exclude some third party services and programs. In addition, temporary disable antivirus and UAC on Windows 7. Also make sure the printer driver is support to Windows 7. Furthermore, you can try to create another administrator account and login to see if the same issue occurs. Hope that helps. Regards, Leo HuangPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

another real basic troubleshooting step before we go on: Have you run sfc /scannow at the command prompt? This is a local printer I assume because you said it was your family's PC and it is not networked correct? It is pluged in via USB or are you printing wirelessly? What kind of print is causing the issue? Real odd thing I just came across the other day too: IE 9 caused Office 2010 to not work at very random times. See if you take IE 9 off and bring IE 8 back through the Windows Updates control panel applet if that helps at all (a shot in the dark but worth a try). Oddly worked for me and our Office issues here.

another real basic troubleshooting step before we go on: Have you run sfc /scannow at the command prompt? This is a local printer I assume because you said it was your family's PC and it is not networked correct? It is pluged in via USB or are you printing wirelessly? What kind of print is causing the issue? Real odd thing I just came across the other day too: IE 9 caused Office 2010 to not work at very random times. See if you take IE 9 off and bring IE 8 back through the Windows Updates control panel applet if that helps at all (a shot in the dark but worth a try). Oddly worked for me and our Office issues here.