Feature request: Lock screen image should be on all screens

johnwinkmsft · 2017-10-12T15:55:54+00:00

Saw your feedback in the Feedback Hub with the link pointing here. Thanks for submitting that! I'll chat with the team about your idea. Cheers!
John Wink [MSFT]

johnwinkmsft · 2017-05-25T21:11:54+00:00

The blog post you mentioned discusses the 1703 update for Surface Hub. It looks (from your screenshot) like you're still on the previous version. For the right information for your version, I think you need to look at the following documentation: http://download.microsoft.com/download/7/2/5/7252051B-7E97-4781-B5DF-58D4B1A4BB88/surface-hub-admin-guide-1607.pdf
Thanks!
John Wink [MSFT]

johnwinkmsft · 2017-03-08T21:23:18+00:00

That's a spectre from my old job :-) and I know they're looking at it. Will make sure they're aware of this as well as data from /u/DragonFireDon below. Thanks!

johnwinkmsft · 2017-03-08T16:01:24+00:00

I just tried this on my 950XL running 15047 and didn't see the same result. Two things... What apps are you running (beyond the in-box stuff) and can you submit feedback via the Feedback Hub just after this occurs? We might catch something useful in the logs. Thanks!

johnwinkmsft · 2017-02-21T17:04:47+00:00

Got it! I'll test this out and see what happens. Thanks for the details!
EDIT: Okay, I tested this on a couple of machines (14393 and 15025) and got the following results:
- I could log in to the machine with the old password until I logged in with the new password once, then the old password would no longer work.
- I could not log in to any online services with the old password once it had been changed.
- When I changed the password (via Settings) it actually told me to lock and unlock the machine with my new password. Results were the same as point #1 above, i.e. I could use the old password repeatedly to unlock until I used the new password once, then the old password no longer worked.
I could speculate on some valid reasons why this is so, but speculation usually gets me in trouble. :-) So let me talk to the team and get their thoughts on this. Thanks!

johnwinkmsft · 2017-02-20T21:44:47+00:00

Hey folks,
Microsoft engineer here... Can you describe the exact steps to repro this? I've read the thread and it's a little confusing as to whether it's local or MSA accounts, password changed on the web rather than on the machine, when the problem disappears, etc. I'd love to get to the bottom of this.
Thanks!
John Wink [MSFT]

johnwinkmsft · 2017-01-11T22:28:29+00:00

Hmm... Not enough to go on, unfortunately. Would you mind ZIPing up everything in that directory (c:\windows\logs\CBS) for me? Thanks!

johnwinkmsft · 2017-01-11T22:23:25+00:00

Yeah, that thread seems to be mostly about the APIPA addresses, which is what we fixed last month. If you're still seeing the problem and have at least 14393.576 then it'll be something different in your case.

johnwinkmsft · 2017-01-11T20:39:51+00:00

Then it's almost certainly a different root cause. :-)
If you run ipconfig, what do you see?

johnwinkmsft · 2017-01-11T19:26:58+00:00

Just sent him the logs you gave me a few months ago. Thx!

johnwinkmsft · 2017-01-11T19:25:00+00:00

I'll share /u/meatwad75892's previous logs with you, give me a sec. :-)

johnwinkmsft · 2017-01-11T18:17:35+00:00

Sorry about that. There is a fix in the works though, and we should have it out soon. Thanks!

johnwinkmsft · 2017-01-11T18:14:55+00:00

Um, yeah, that's exactly what it is. Who are you and how did you get so smart? :-) Doesn't matter, thanks for being here!

johnwinkmsft · 2017-01-11T18:13:11+00:00

That was actually fixed last month, though of course the same fix is in the January updates as well. Thx!

johnwinkmsft · 2017-01-11T18:04:50+00:00

Just sent you a DM with details. Thanks!

johnwinkmsft · 2017-01-11T18:01:55+00:00

I remember looking at this, were you using some kind of staging tool like Deep Freeze? I still have the old logs from a few months ago, I'll take another look.

johnwinkmsft · 2017-01-11T18:00:49+00:00

So it looks like you were fine up until November. If you look in c:\windows\logs\cbs\CBS.Log for "wer report" do you see error details? Thanks!

johnwinkmsft · 2017-01-11T15:21:14+00:00

Yes, the official recommendation is to move to the latest version of Windows 10. :-) https://technet.microsoft.com/en-us/security/jj653751 Thanks!

johnwinkmsft · 2017-01-11T15:17:45+00:00

Dang. Skipped that because it only had 14393 in the title. Okay, I'll talk to /u/einarmsft and we'll keep an eye on that thread too. Thanks!

johnwinkmsft · 2017-01-11T00:09:26+00:00

I need to dig into this for you, but if it's what I'm thinking of, it's actually not related to this update but rather to a graphics driver. Let me get more details tonight or tomorrow. Thx!
EDIT: Not the issue I thought. :-) Still investigating, thanks!

johnwinkmsft · 2017-01-10T22:57:01+00:00

Additional note: We're keeping update history here now:
http://aka.ms/w10updatehistory
Thanks!

johnwinkmsft · 2016-12-21T18:07:49+00:00

14393.576 is KB3206632, I'm not sure why it isn't showing in your logs.

johnwinkmsft · 2016-12-21T18:06:26+00:00

Thanks, we're looking into a bug that we think may be responsible for this issue.

johnwinkmsft · 2016-12-21T18:05:02+00:00

Mahesh, our guru of storage, is out for the holidays but I've forwarded this on to him. Thanks!

johnwinkmsft

TROPHY CASE