Currently I am having an issue with Windows 10 on my Surface Pro 3 asking me to verify my Microsoft account inside windows 10 (ie. Re-enter credentials Notification pop-up), even though I verified previously when I setup me Windows 10 on my Surface Pro 3. This is my second replacement Surface Pro 3 (this one is with Windows 10 pre-installed) and still it prompts me to verify every now and then. I think I have found the cause however Surface support do not seem to have any way to escalate this, so I thought I would post this here for other people to check. What I have found is sometimes when I boot my Surface Pro 3 and login to Windows 10 that the Surface Pro 3 serial number is not accessible to the Operating System. This can be checked by either running the Surface App (from the MS Store) and going to the page with all the system info (serial number will be all zeros) and/or going to a windows command prompt and typing: WMIC CSPRODUCT <Enter> (and it returns No Instance(s) Available, instead of all the system details including the serial number). When this happens after boot 100% of the time I am asked to Verify Windows and enter my PIN (since I have PIN entry enabled). Then should I reboot my Surface again and this time the serial number is available, via the methods mentioned above, then you guessed it Windows 10 prompts me to Verify again. Obviously if the Surface boots in the same state (when the serial number is available or not) then I do not need to verify (ie. it is only when the serial number switches to not available from available and also from available to not available that the verify prompt is raised). Is it possible for other users with this problem to test my findings to see if you see the same? Perhaps then Microsoft Surface support will not keep saying this problem is just my problem. FYI: I currently have an open case with Surface Support (for the Australian region). I have tried a complete reset of my Surface Pro 3 and still the problem happens. I have tried switching to a local account then back to my Microsoft account and still the problem happens. So no solution as yet. Currently my SP3 is running the firmware dated 15th September 2015, since Windows Updates currently does not provide to me the 29th September 2015 firmware and I cannot manually download this firmware to try it out.