12-24-2018 02:16 PM
Both cameras on my Lenovo Yoga Book (Win10) have their images rotated by 90 degrees. This can be seen in the Camera app, where by the way clicking the settings button generates an exception (see image).
Reinstalling the driver (AVStream) and so forth did not help.
This seems to be kind of new, possibly connected to the latest win10 upgrade?
Anyway, this issue renders the cameras useless for Skype etc.
12-25-2018 10:44 AM
This is not a problem specific to your device. This is a common problem with the latest camera app updates. I don't know what is Microsoft waiting for to fix this issue.
Have a look at this thread:
12-25-2018 02:01 PM - edited 12-25-2018 10:27 PM
Thanks for the quick response and helpful link.
So I will have to wait - though I'm not all sure whether this is a Microsoft issue; might also be a Intel driver problem.
12-25-2018 11:00 PM
though I'm not all sure whether this is a Microsoft issue; might also be a Intel driver problem.
It has to be a Microsoft issue because the camera app and the rotation of the image were working fine prior to the latest app updates from the Microsoft Store.
The update before the latest one added a feature to select the rotation degree manually, and the latest update seems to fix the automatic image rotation, and removed the feature to select the rotation degree. However, when I click on the settings icon in the camera app, it crashes with the same error you have posted earlier in your thread.
It's also worth to note that I have not updated the Intel HD Graphics driver before experiencing this issue - so it's not an Intel driver problem.
12-26-2018 07:20 AM
I see your point, but it might still be a problem of the driver not adhering to the specification. Don't know if the problem occurs with non-Intel cameras but I would say it's quite unlikely that the bug goes unnoticed if all cameras were affected.
Anyway, we will have to wait for someone to fix the issue or provide a workaround (specifying the rotation).
02-26-2019 09:58 PM
Hi Bentsch, I am having the same issue and have been unable to find a fix. Have you had any luck in resolving the problem, it's now more than two months since your last post on the matter so I'm hoping you may have resolved it and could let me know how?