This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
I am using O2010 Professional Plus UK. It seems that O2010 ignores all setting of the Properties of the printer and only applies the settings you see on the print page of Office itself. That means that all other options of the printer are out of reach: O2010 just ignores them.
This issue is only with O2010 and not with any other software so it clearly must be an O2010 problem.
I am using a Vista 32bit UK OS.
Any help in solving this is more than welcome!
Michael
A family of Microsoft word processing software products for creating web, email, and print documents.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
It suggests an incompatible printer driver or the driver is damaged. Download the latest version of the driver, then delete and reinstall the printer. If it persists, take it up with the printer manufacturers support site to see if they have a solution.
-- Terry Farrell - MSWord MVP
Problem: Microsoft Word 2010 ignores printer settings when in Compatability Mode. When in Word 2010 mode it prints fine. For example: try printing 2 copies, or a page range, current page or anything else in any compatability mode document created in any verson of Word and it does not work. It will print a full copy of the document. But it ignores everything else.
Temp fix: I have people convert the document to Word 2010 format to do any kind of special printing. If they want the page range or 2 copies or anything else it has to be done from Word 2010 format.
Keep in mind that Word 2007 DocX format is Different than Word 2010 DocX and so 2007 docs come up as compatability mode as well and have the same issues as any other .doc docs.
MS should fix this. I know office 2012 is about to release, but this is a really bad bug. I have this issue on brand new images running Windows 7 Pro (updated), Drivers for all the printers updated, and the issue is happening on all the many types of printers we have. Not a driver issue. Word issue.
By the way, the version of Word 2010 is the corporate version with sp1 built in. Not sure if that makes any difference. I don't have 2010 without sp1. Maybe that has less issues. Curious if the guys not experiencing this are running a previous version of 2010.
Chris
I know this is an old post, but have exactly the same issue. Unlike MS to accept any responsibility for their products...... This is definitely not a print driver issue. Print drivers are working fine for all other applications, just MS Word & Excel 2010 that has this issue...... All default settings worked correctly until we upgraded to Office 2010 (what a strange coincidence.....) Let me guess, there will be a post regarding print drivers being damaged. There has also been a long standing issue, with MS documents being flagged as colour documents (even though there is no colour in the whole document). Not only does this cause problems for users that don't have access to print in colour, documents that have no colour in them are being billed for a colour print. Top stuff MS!!!!! Look forward to another lame response!!
At first glance, Terry Farrells answer seems a too easy, but in our case he turned out to be right.
We use HP's Universal Printing Driver for all printers. Using Word 2010, Excel 2010 or Powerpoint 2010, printer properties would not be applied.
After installing a new UPD version (5.2 - nov 2010), our problem melted away like the snow outside. Which means slowly, leaving a mess...
I am not sure that KB Article deals with the particular behavior that was the issue in this case - the secure print option being ignored.