Not sure if I'll mess around with it much to be honest.
I can't log into that workstation for some time over the weekend (it's a lab that's shared), so I'm not entirely sure. These are my results:ĭoes anything show under System\Advanced System Settings\Advanced\User Profiles\Settings? I deleted the account on my VM and then ran sysprep /oobe /generalize. It should be created, but disabled (which makes it even weirder that Windows was trying to log in as DefaultUser0). There is nothing about DefaultUser0 that I can find anywhere on that image. Only 'admin' and 'student' are local users. There's no DefaultUser0 to delete in local users. Either way, both accounts have passwords. I learned about the video issues the hard way by doing that when I first set up my golden image. You can leave the password blank when you initially set it up. I mean you can set it to autologin I believe, but you still had to set some kind of password up initially. They both have passwords set (I thought Win10 actually requires something to be set). Something about HyperV using RDP and RDP not liking passwordless accounts. I can't find the article, but it can cause video issues. You can remove the account with no ill effect.ĭo all of the accounts have passwords set? If not, make sure they do. I've seen a few things suggest that it's created when something goes wrong within Windows, but nothing definitive. Nobody knows why it's created or what it actually does, but it only exists on the Anniversary Update. This has happened on 4 completely different hosts (laptops/desktops/CPU architecture/etc).Īrticle in February was from Joseph Hogan. Just putting that out there for the memory bank. Doesn't happen with any other OS, just Win10. I think it has something to do with the video. in general, let it create a SID and stop looking for the network.
The local accounts are 'admin' and 'student'. One weird thing is just before it cuts to white, I noticed "defaultuser0", which I didn't create. I started getting the same thing during a brand new VM on a differencing disk, with a parent Win 10 (this is for a lab, hence differencing disk instead of dynamically expanding). There was a Spiceworks article back in February that said someone was displaying a white screen after sysprepping.
0 kommentar(er)
