Problem still continues. I didn't know this thread existed, didn't go past page 1 of the Windows 10 forum, my bad. So I started up a 'Loopy' thread.
If you look at page 2 of the Microsoft Insider link that Ewol posted above post#1, allegedly some find relief by, as Graham Newsome there put it on June 6th,
Try going into your BIOS Setup (ESC, DEL, F2 or whatever on Boot).
Set Non-Execute Memory Protection to ENABLED.
This has worked for the majority of users with this Looping problem.
4 people found this helpful
So now I'm doing that, but I suspect another problem is that RAID should be off. If you'll recall, for Win7 RAID had to be on, or the OS wouldn't run. For Win8, the setting had to be changed to AHCI. So why wouldn't Win10 secretly have the same need?
Gonna stay up a few more hours and see if the looping stops. For I have no prior build to go back to.
EDIT, RESULTS: it doesn't help, but at least it was slow enough for me to get it into repair mode, by changing RAID to AHCI, so I could get into command prompt.
Here's what's happening:
- the loop means, at each reset, Windows creates a new windows.old file. I had EIGHT of them, even though I did a bare metal installation to a drive which was brand new (no files ever on it, I installed the drive myself).
- Suddenly the MBR gets assigned a drive letter of 'C',
- and the recovery partition of course remains 'D' (holding all those windows.old files).
- E drive becomes what should have been C drive.
- Since this isn't DOS anymore, I can't do a redirect or substitute on the letters.
- The MS forum ideas don't work, because, inter alia, bootsect.exe has to know the drive letters.
But maybe there's another fix. Gonna try something before explaining more.
EDIT AGAIN: the solution I'm trying (after renabling RAID) is the 'bootsect.exe' on page 2 of post #1's link. Problem is, I don't know if nt60 or nt52 should be used, but I did nt60 and it said everything got repaired (doesn't mean it's true).
EDIT AGAIN 6:28 am CT: I thought that if I could get it into Command prompt from Advanced options, that I could trick the system into just accepting reassigned drive letters using diskpart and assign. I was able to reassign the letters, but found out that only portions of the directories which should have been on the e re-assigned to C windows drive, were there.
So the loop keeps looping, also because not all the programs are installed.
This is hopeless, sorry I took the plunge but at least I can say I tried to make it work.
This 'Preview' never should have been released. NO quality control. So the 'new' version is not worth any more of my time. I should bill Microsoft for my time. So should we all. Even freeware is better than this.
Edited by brainout, 29 June 2015 - 06:32 AM.