Windows 10: your pictures can't be printed because this error occurred. See pics

I get this error when I try to right click an image and select print.
your pictures can't be printed because this error occurred. in 5 different windows. please see pic.



OS is win 10 Ent. with Fall creator update and all recent patches.
I have no other issues in regards to printing.
All my printers are network printers.
This issue is not present if I use a different logon and hence a different profile.
I have so far:
sfc /scannow No issues
dskchk /f No issues
dism.exe /online /Cleanup-Image /StartComponentCleanup No issues
DISM /Online /Cleanup-Image /RestoreHealth No issues

I am thinking it is profile issue and have tried instructions on Fix: Corrupt User Profile in Windows 10 and did not help my case.

Any other ideas are welcome. I prefer not to create a new profile and start from scratch, for just this issue.
Thanks in advance for any help.


:)

 

windows10 photos can;t print pictures

Bottom of the page where? There is no print option in the Photos app that I can see and Microsoft Pictures isn't part of the office suite anymore.

**After my initial post, I found that if you option one picture, you can print by clicking the ... option in the upper right to see more menu options, including printing. This didn't occur to me to try because I'm trying to print out 12 photos. This is
a pain that I can't select multiple pics and print them at once.

 

"windows photo viewer can't open this picture because you don't have correct permission to access the file location"

Original title: access permission

Hi

I am using win10 and when I want to see my pics I cant because there is an error

"windows photo viewer can't open this picture because you don't have correct permission to access the file location"

what should I do??????????/

help me

 

According to this article: Solved your picture can not be printed because of this error

..and the quantity of those error messages, it seems you are trying to print multiple pictures at a time, yet your computer may not have enough memory to process them (I'm sure your computer is still fast)
So, try to print one picture at a time. Does it work this way?

*Edit*
I apologize, I didn't read everthing you wrote; I just looked at that picture and looked online to why that happens.
I read your post now. Your user account 'could' possibly have too many programs that open once you log in.. so do try my method of printing one at a time. If that works, then most likely that means that you have many programs open at once and apparently printing many pictures needs a lot of memory. You can close a lot of the opened background programs and try printing many pictures at once. YET on the other hand, if you still cannot print one at a time, post back here please.

 

Thanks for reply pepanee,
No that is not the issue. This happens regardless of how many pictures I choose, even one.
There is plenty of Memory and CPU available.
My other profile can do 12 or more pics with no issues.
That is why I think it is a profile issue.

 

You're welcome. I see what you mean now. Yes it is definitely most likely the account profile then.

• Try reinstalling the printer, maybe some setting in your profile got altered in a way that causes the error.
• Also, it seems that you're an advanced Windows user. Open the Event Viewer, then try to make another picture print job (to get that same error). Once you get that same error, look at Event Viewer's Custom Views & Windows Logs. Most recent log is on top. See if you can find it in there to see if the Event Viewer logged this information down, since usually it has a lot more information on errors. We can see if then we can narrow it down to see why you get that 'blank' error.

 

Yes it would make sense, however nothing related shows up in app, admin, or sys logs.
Also have tried uninstall reboot, remove drivers of printers and that has not helped either.

 

My bad now I see two events being generated after print attempt.
This is in Admin log.



Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c001d. Server error: empty. Debug Output:\r\n joinMode: Join
drsInstance: undefined
registrationType: undefined
tenantType: undefined
tenantId: undefined
configLocation: undefined
errorPhase: discover
adalCorrelationId: undefined
adalLog:
undefined
adalResponseCode: 0x0
==============================
Automatic registration failed. Failed to lookup the registration service information from Active Directory. Exit code: Unknown HResult Error code: 0x801c001d. See Azure Active Directory Documentation - Tutorials, API Reference | Microsoft Docs
=================================
I found this which I am going to try and will post after reboot to see if it worked.

'm seeing the same errors (Event ID 304 and 307) in Server 2016. The Scheduled Task "Automatic-Device-Join" is located in: Task Scheduler Library\Microsoft\Windows\Workplace Join. The task calls %SystemRoot%\System32\dsregcmd.exe.
The work-around is disable the task or configure the GPO Computer Configuration > Administrative Templates > Windows Components > Device Registration.
Appears to be oversight/bug in Windows 10/Server 2016... awaiting resolution from Microsoft.
Below is Help text from the GPO:
This setting lets you configure how domain joined computers become registered as devices. When you enable this setting, domain joined computers automatically and silently get registered as devices with Azure Active Directory. Note: Additional requirements may apply on certain Windows SKUs. Refer to Azure Active Directory Device Registration Overview. How to configure hybrid Azure Active Directory joined devices

 

Rebooted, retested and still the same.
Note: We do not use roaming profiles.

 

Hmh.. wow yea. I just searched online for: 0x801c001d
And I saw all these results. Hopefully it's not a complicated process to fix. I would suggest you search online for this from the error you get: 0x801c001d

It seems that it could be related to the roaming profiles thing you stated. I would suggest trying attempted solutions from other users you can find. I wouldn't know what to do from here.

Hopefully someone else has better insight on this and posts here.