Even killing UAC (which btw has been proven useless at preventing programs doing whatever they like for YEARS) doesn't f**k things up as badly as simply trying to use the actual Administrator account. Broken by design. Windows 10.
Nothing to do. Wait ~ 2 minutes with this message, switch you PC off. Then switch it on, you'll see for a few moments the login of "DefaultUser0" then you'll be prompted to login (create your account). Go ahead and pray to have this as the last problem in 10147.
Just to get it clear for me is this not the windows 10 driver ? proberly not just wondering Grtz Base
Yeah I know have did a sfc /scannow and also found some problems ! Proberly my video driver is cousing the BSOD but it is the latest I can find
I think thats why they havent released a build yet. they are pushing for rtm. thats the way it look. there is only about 35 days left.
And notice that very few builds has been compiled in other branches, this it could mean that maybe they are approaching to the rtm.
UAC: Well, it's there for convenience first of all rather than security. The benefit is that you don't need two separate accounts (standard and admin) anymore and switch back and forth between them to perform administrative tasks. UAC forces an admin account to run with standard user rights by default and prompt you for elevation when necessary. While it definitely has something of a security feature, I think it's a common misconception that it was there to prevent you from malware etc. They introduced it because many people used to have the habit (or still have) to operate only under an admin rather than a standard user account, which is not a good idea because just about every application will be able to access and change anything system-related and that is a possible security threat (it's just like using the root account for everything under Linux). So, if you disable UAC, at least make sure your main account is a standard user and not administrator (for your own sanity). This will ensure that no application can access anything that requires administrative priviliges in the background without your notice, and effectively protect you from the kind of malware that targets that specific vector. But whether you use UAC or not, there is no protection from malware that is using technics to do harm in standard user mode (botnets etc.), other than anti-virus etc.
At present installed on my Win7 laptop in VirtualBox with 1Gb RAM and 20Gb VirtualHDD. Seems to be running pretty well. More like a MobileOS with Privacy and Apps etc type of settings, turned off everything not needed. Now having confidence to try on a extra desktop.
I rebooted my machine and booted into my windows 8.1 install and logged in, but decided to reboot and boot back into my windows 10 install. now it wont log in. I enter my password and it just sits there with the spinning dots. HDD activity stops and dots still spin. waited about 10 minutes and hit reset. and it got stuck at the screen again. I have no problems logging into safe mode.
it's works on lenovo x230 (10130 was not deployable) annoying bug found in 10135 (windows explorer window opens 2-3 mins because of quick access has smb links): fixed notification center works/opens again (it was nonworking in 10135) and I could deploy oldschool cisco vpn client what was broken in 10130. BUT lenovo biometric logon (fingerprint) nonworking, i guess final biometric framework will require different than win8x drivers/apps in RTM.