Home Dashboard Directory Help

Cannot change LockScreen image for application target type of x86 or AnyCPU on 64 bit system by devicedriver


 as External Help for as External

Sign in
to vote
Type: Bug
ID: 729780
Opened: 3/8/2012 10:43:23 AM
Access Restriction: Public
User(s) can reproduce this bug


I am attempting to change the lock screen image using the Windows.System.UserProfile.LockScreen.SetImageStreamAsync method. On a 64 bit system, when running the application targeted at 'x86' or 'Any CPU' platforms, it works successfully the first time and then stops working. Registry logs seem to suggest that a change is being made to HKCU as opposed to HKLM when this call is made. This is visible when you check PC settings and notice that your lockscreen image in settings shows that a change has been made but this is not visible when you actually lock the system.

When switching to a target type of x64 however, this works consistently all the time.
Sign in to post a comment.
Posted by Truong2D on 6/11/2012 at 2:00 PM
It seems that the test owner had missed a basic test case for this API:)
Posted by Microsoft on 5/9/2012 at 1:06 AM
Thank you for your bug submission. The issue you reported appears to be a Windows issue, and we have forwarded the bug to them. We will close the bug in Connect, as they have now received it in their internal database, and they will evaluate it for the product. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com <http://support.microsoft.com/> or call 1-800-MICROSOFT for assistance. For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

Other Support links - http://support.microsoft.com/ph/14019#tab13
Posted by devicedriver on 4/2/2012 at 9:51 AM
Any updates on this issue?
Posted by MS-Moderator01 on 3/8/2012 at 11:59 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.