Same problem. Spent hours with Microsoft tech support who charged me $99 and they couldn't figure it out. Well, guess what, they are just not as competent as I would like them to be as I finally figured it out myself. The problem is that for some reason, you
have to run Office app (or any app you have printing issue) as an Administrator in Windows 10. And here is how you make it happen:
How to fix printing issue in a Window 10 application:
(1) Go to the application tab from “Start”
(2) Right click on it
(3) Go to “More”
(4) Select “Open file location”, this will take you to file explorer directory where your app is
(5) Right click on the highlighted application name, select “Properties”
(6) Click “Advance” button
(7) Select “Run as administrator”
(8) Save all changes
(9) Recreate all shortcut, re-pin to task bar etc
Don't forget to do (9)! Now your app will print. But there is a pesky but harmless side effect in that you will get a UAC prompt everytime you open the app. Just click "Yes" on the prompt. If you don't mind that then you're done. If you want to get rid of the
UAC prompt (for a single app), you have to use the Task Scheduler. Here are the steps I found on the web.
(1) In Task Scheduler, right-click "Task Scheduler Library" and select "New Folder" Name it whatever you would like.
(2) Select the new folder and click "Create Task" (not "Create Basic Task")
(3) Name the task something descriptive. Enable "Run with highest privileges," and select your OS under "Configure for."
(4) Under the Actions tab, select "Start a program" in the Action dropdown if it isn't already. Click Browse and find your app's .exe file (usually under Program Files on your C: drive).
(5) (Laptops) Under Conditions tab, deselect "Start the task only if the computer is on AC power."
(6) On your desktop, right click and select New > Shortcut.
(7) Paste 'C:\Windows\System32\schtasks.exe /RUN /TN "Name of folder\Name of task" into the text box.
What a pain in theAss!!! This is a just stupid stupid bug that wasted hours and hours of my time. Microsoft should be ashamed of themselves to have bugs like this in the year 2015. Don't they even do QA on their products? Or did they only do it in Adminstrative
mode? I'm not even a tech guy, I work for a hedge fund. The fact that as a tech layman, I have to figure all these out all by myself wth no help from those Microsoft tech support (after they have the nerves to charge me $99) says plenty about the company.
So glad we don't have MSFT in our equity portfolio!
(