You should have done clean installation of 9841 and upgrade to 9860. The problem is possibly emanating from the recent 9860 ISO you used for the installation .
1) The ESD is converted to ISO which you even stated in number one of your post. That is what I am talking about. 2) What I am driving at is that if he has to do upgrade at all he must make sure previous installation is in good condition. I am a proponent of clean installation in this forum. 3) You run your clean installation on VM and the installation file you used could be different from his. Stop begging the question though.
Yes, sir! My suggestion is to make sure he does clean installation of previous build that has a complete ISO from Microsoft before doing the recommended upgrade(I think that is the reason for no ISO in the first case by Microsoft). I wouldn't know but I am only speculating. That is clear from my use of the word 'could'. No, I didn't mean any harm. I am just stating the obvious.
Yelp! I completely comprehend that from his post, Sir. I only suggest he does clean installation of previous build 9841 and upgrade to 9860 and see if the problem would go away.
Copy that. Error was reported in relation to upgrade and fresh install likewise. As i and some others don't experience it, i would assume it's not a general problem of either upgrades or fresh installs. ...
slave, type your password wrong and what do you see? I don't have ToiletPaper installed atm so hard to tell what I'm missing. ^_^ Looks like he typed the password wrong and its offering options. -ed- or is that the ONLY screen he is getting? (he she whatever lol)
Was referring to the error with the doubled LogIn picture/account thingie (reported by naseap and others) .
Just to add. I have set my account to auto-login. Are you on auto-login as well? If not, try setting to auto-login and see if you can reproduce the bug. Thanks!
OK ... can reproduce it . Starts when activating auto-login. Although i must commit i never use that feature as it stores the data afaik still in pain text in registry . Better use the SysInternals solution.
I can confirm that the double login picture is from activating auto login. I disabled it and it went away. Enabled it again and it is back.
That's correct. Most of the upgrades, if am right,with the error have been tweaked in previous build one way or the other by the users. That's the very reason I speculate in the first place. Having found out lately the culprit is auto-login process, it is palpable this whole error thing is more or less a squabble at the end.