do you know what it is supposed to fix,i didn't notice anything,would expect them to at lest fix the menu bug with crazy icons.
I been wondering about something. currently right now I have dual boot system with windows 10 preview and windows 8.1 1. when windows 10 is finished and release, can I just upgrade over my windows 10 preview and keep my windows 8.1 install? 2. that I would need to use my windows 8 key for windows 10 activation over the insider preview? 3. would I loose activation for my windows 8.1 install?
.It is well documented that licensed users of W7, W8 and W8.1 will get to move to W10 for free within the 1 year time frame after official release. The Enterprise edition is not included. It is also stated that W10 Technical Preview users with the proper prior license will get to stay with W10 without the need to revert back to prior edition and then come forward gain. So yes, as it stands now, you would need valid key.
anyone having problems with data loss and some bluescreen from NTFS_FILE_SYSTEM? at least I got a permanent backup using btsync so I could go back, but 10122 is much more buggy than 10074 was. what's really curious is that microsoft didn't already find out there's a serious NTFS problem. you can try it for yourself: boot up windows 10 and then just reboot to windows 7 and check the windows 10 volume using chkdsk. you'll get errors everytime at a reboot!
I've came across somebody else who mentioned this although I was unable to recreate it. Their solution was to turn off Fast Boot in Windows 10.
Downloaded the ESD, converted and did a clean install....and in less than 12hrs I'm on my way back to Win 7 for now. Long delays when launching system apps like File Explorer or Chrome...sometimes I can click on icons and get nothing - no indication of launch, no changes in Task Manager, just nothing. Hardware Sound with my Xonar D2X will just start cracking and stuttering in the middle of apps Serious mouse speed changes - my mouse icon will literally go from slow to super fast and back to slow I've sent in feedback on all the issues, but I can't use this as a test bed so I'm going back to 7 for now. Maybe in a few builds..... T
That's a very old bug and originated with Windows 8, actually. I had it...the cure for it is simple, but I can't recall it at the moment--sorry--but just Bing/Google it (not as a Win10 problem but as a Win7/Win8 dual-boot problem)...the solution for Windows 8 works with Win10, too.
That's a decent list, but I'd only suggest leaving out RT and Win Phone...Windows 10 as in build 10122 is nothing like either WinRT or Windows phone... Microsoft is trying to take Windows Phone users to something called "Windows 10" but it is nothing at all like the code for the Windows 10 we're running in 10122... I'm really not sure why Microsoft wants to do this as the two OSes will be alike in name only--! I guess it's a marketing ploy.
What are the specs of your pc. Without knowing this it is difficult to try and offer advice on your issues.
...sorry about that... Xeon X5680 @ 3.33GHz ASUS P6T SE - current bios 6gb Ram Xonar D2X Sound Card nVidia GeForce GTX 670 2gb 1x SSD 3x HD
This you for this information, it was not a simple matter find it in my searches! I hope that it goes into into the search databases that keywords Install.esd and $Windows.~BT and sha-1 and checksum will reveal this post for the sake of posterity. In an effort to contribute something (though probably useless), here are the checksums for my Install.esd for build 10122: SHA-1: 824f295dc4680b2ef3d52fc0bacd5baa0ad0c029 MD5: a749062ed3653757f7519b12fb7668c0