Announcing Windows 10 Insider Preview Build 14316 Insider
-
WARNING - be wary of going into safe mode.
Went into safemode via msconfig boot option and had a flashing desktop with an error flashing as well. With much effort I found the error said, "Get Started app can't be opened with the Built-in administrator account. Sign in with a different account and start again".
I had signed in with my MS account as per usual.
This happened with both my 14316 comps.
I struggled to work out a way of getting back control as the flashing didn't allow me to run msconfig again or do anything much else. Winkey/R didn't work either.
In the end I booted with my trusty win boot disk and got up the command prompt.
I ran "bcdedit /deletevalue {default} safeboot" then rebooted. The comp did a disk check on restart and came up normally.
If you want to get into safemode, be prepared for an emergency strategy!
-
-
Another note, the second comp stopped flashing after a bit and displayed an error box titled "explorer.exe - Fail Fast Exception"
Then, "A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately".
Exiting that error box started the screen flash again.
This second comp was also got going with the bcdedit command and there was no chkdisk at startup.
-
Thanks for confirming this. I was really wondering how it is only me that have this app.
So I've uninstalled it and I've got this:
Was this there before?
Both are in build 14316 under optional features.
-
WARNING - be wary of going into safe mode.
Went into safemode via msconfig boot option and had a flashing desktop with an error flashing as well. With much effort I found the error said, "Get Started app can't be opened with the Built-in administrator account. Sign in with a different account and start again".
I had signed in with my MS account as per usual.
This happened with both my 14316 comps.
I struggled to work out a way of getting back control as the flashing didn't allow me to run msconfig again or do anything much else. Winkey/R didn't work either.
In the end I booted with my trusty win boot disk and got up the command prompt.
I ran "bcdedit /deletevalue {default} safeboot" then rebooted. The comp did a disk check on restart and came up normally.
If you want to get into safemode, be prepared for an emergency strategy!
You are not alone! Go to Feedback Hub or Feedback and upvote the numerous references to feedback unstable/dont work/unusable/flickers and so on
-
-
I know I asked this before but, do we all concur that file and folder names are now margined to the left in this Build?
Attachment 74042
You are correct Edwin, file/folder names are left aligned. They are still centered on desktop.
-
Discovery regarding this latest " beta build "
(01) Boot time considered slower
(02) Try running gpedit.msc
(03) Few more added Logs or errors then the previous
(04) Noticed Freezing attempts (clean install)
So there are still lots of issues that need attention and to be worked on the next current beta build and some of them I listed are not simple fixes will require lots or wrench time and trouble shooting labour extensive.
Last edited by AcuraTML; 10 Apr 2016 at 10:50.
Reason: Added more Information
-
As I mentioned a few posts back, the update came last night on my main PC and at the last stage of installation, it popped a recovery blue screen. It's like it suddenly lost communication with the hard drive. So, I reboot to my 10586 main OS and I noticed that the SSD where I have my insider build is not showing in the explorer. So, I opened up a partition tool and found out that it has no drive letter assignment. After assigning a letter, it still won't boot up so I restored it back to 14279 image and tried the upgrade again (this time from ISO that I created from the ESD) to see if I will get the same issue. Otherwise, I will do a clean install. But the upgrade went through the second time around. I think I will keep it this way because the restored 14279 image was a clean image anyway. So far, no other issues popping up.
-
First, let me apologize if the "screenshot" isn't big enough to see. The only way I could get a screenshot was to PrintScreen and then use the snipping tool to only show what should be shown. 
For the life of me, I cannot figure why I'm getting this; it has never happened before, but is now happening with Build 14316. I have tried clicking the box in "Always open with this app" but that doesn't work either.
Edit: Well, it's good to know that the way I had to do things worked this time. :)
-
First, let me apologize if the "screenshot" isn't big enough to see. The only way I could get a screenshot was to PrintScreen and then use the snipping tool to only show what should be shown.
For the life of me, I cannot figure why I'm getting this; it has never happened before, but is now happening with Build 14316. I have tried clicking the box in "Always open with this app" but that doesn't work either.
Try setting it from Control Panel\All Control Panel Items\Default Programs\Set Associations Wynona. If it's a file tye you want only Firefox to open always.
-
-
Try setting it from Control Panel\All Control Panel Items\Default Programs\Set Associations Wynona. If it's a file tye you want only Firefox to open always.
I have Firefox set as my default browser, Cliff. As far as I know, it should always open everything, but it's not working right.
I can come into TenForums without issue. I can open links from some emails without issue, but others will give me that window. There are too many of them to be forced to set associations for each and every link I follow.
Since there don't seem to be any others having this problem, it may be unique to my system?
Quote
