New
#131
9879 seems speedier too, although I had 9860 bloated to the max with a ton of software!
9879 seems speedier too, although I had 9860 bloated to the max with a ton of software!
Edwin, where are you coming up with that? Are you running in a VM? I have no such structure.
Attachment 8305
When set to "View by Large Icons" it seems folders that contain sub-folders have the old look, but folders with just items have the new look.
EDIT: Any view shows half and half!??!
Seems like my system is pulling icons from shell32.dll when most of the new icons are in imageres.dll
I use it on a TEST machine only. At first I thought it was safe enough to install it on a separate hard disk drive, and just select an operating system at boot up. Then 9879 misbehaved and trashed a Windows 7 OS installation on a completely physically different hard disk than the one I was using for Windows Technical Preview.
From now, I am running Windows 10 ONLY with my other hard disk physically disconnected. I don't trust this OS yet, for good reason.
But it seems to run OK. Just doesn't play well with others. The OS operates a lot like Windows 8.1 to me.
Wish we could have seen Disk Mgmt screenshot as in a Dual Boot one OS or the other holds the only set of boot files if installed with both HDs attached. So Win7 may have only needed its boot files restored first, or adding back to Dual Boot using EasyBCD.
Or is there another way that Win7 was affected? Have you seen other complaints indicating it's a pattern? As of yet I have not and I deal with complicated Multi-boots every day.
Nope, it wasn't a boot manager thing. I was choosing my boot drive using the motherboard bios, not a multi boot boot manager.
Disk manager saw the drive as EMPTY, not even partitioned or formatted. I switched to a Linux OS and saw the same for that poor little Windows 7 OS drive. There was nothing physically wrong with the HD and it had worked fine using the 9860 build. Windows Technical Preview can't keep its hands off other drives in the system, I think.