I've mentioned before, all the "feedback" is about eye candy, but I am sure the SSD issue will be fixed. Still amazes me that the core is second to UI. 100:1 users giving feedback haven't a clue about anything but "start button", "start screen", "Aero", SHADOWS! dunno, we will see soon enough :sigh:
They do have a fix for it. I posted the MS link to the fix back at the end of Dec. 2014. And as far as I have seen and read in the privet MS forums it will be in the CP release.
I am curious about the SSD issue - as Murphy asked, is it with all builds or just the 2 leaked ones? When I think of 'bricked' I think locked up, is this the case here? I have installed several of the official builds, w/o and issues - all on SSDs. 9888 and 9901 installed on SSDs were fine until I started deleting things from the start menus, then the screen started flashing and I couldn't do anything. I assumed it was a Nvidia/graphic issue and uninstalled both builds. Now I recall that when I would re-boot with the drives still in the machine it would say there were errors on the drive and do a"scan and fix". I am now wondering if this was not a graphics issue??? All the SSDs we fine after the "scan and fix" I am currently using 9879 on a Samsung PRO 850 256GB - no problems. I think the drives I installed the unofficial builds were OCZ Vertex 4 256 - not sure if it matters???? Have a Crucial M550 256 - maybe try that - can never have too many SSDs - @WBD - thanks for the info - you posted as I was typing
File hash mismatches with leaked builds 9901 and 9888 I have been seeing mismatches in file hashes throughout my testing but I believe it has only been on the leaked builds. If I download an .iso from Microsoft directly, I get a completely different SHA-1 hash every time. I have also tested copying an .iso from one hard drive to another and the SHA-1 changes once again, every time. Even going back to 9888, I recall Mega.co.nz downloads were also failing at the decryption stage at 99% which was where I first started noticing this. I've had some random CRC failures with 7-Zip as well. The thing is, I have never experienced any issues with file hashes in my lifetime and it has started within these leaked builds in my case. I just wanted to give a heads up to anyone else experiencing this. It may only be specific to certain hardware or drivers, not really sure yet. But definitely something to be aware of. For the time being I am going back to the last supported Insider build of 9879 until the Consumer Preview comes out.
It is not all SSD drives that have the problem. And as far as the other builds leaked or not they have the problem. By what I have read 9901 has the fix in it. Build 9879 does not have the fix and you should in stall the fix from MS before the problem comes up. I did not install the fix and got locked out of my Crucial 250gig drive. Had to use a third party software to get it back. The fix for it is listed on MS site for locked drives.
I do all my testing on a desktop - never hibernates, sleeps, and rarely gets shut off. I use the High Performance Power Setting, display off - never, computer to sleep - never also, under Advanced Settings, Hard Disk, Turn Hard Disk Off - NEVER The issue I have, I now realize is not the SSD. I just installed 9901 on a Vector256GB and all was OK until I tried install Winrar, back to the flashing screen. This has happened with every install of 9888 and 9901 I have tried, it is never triggered by the same thing. It may be something unique to my hardware set up, or my way of doing things. 9879 is fine on a Samsung Pro 850 256 GB and 9879 Enterprise is fine on a Vertex 4 256 GB. Beta software, ya' gotta love it...
All is working great here on my Lenovo Ideapad Yoga 11S (2 in 1) but I have a small issue, the screen doesnt rotate automaticaly and it looks rotation sensor is not installed in device driver. I tried to install drivers from Lenovo but no go. Do you think this is a software issue and TP 9901 is missing this or something else? I can of course rotate the screen manualy but it is nice to have the screen rotate automaticaly. Any ideas? Thank you very much
You must set the driver in Compatibility Mode for Windows 8 or even Windows 7 before installing. That's maybe the only way to get it to work.