New
#30
Opinions are just that, I'm fine with the new GUI.
I really don't see why MS can't be clear and obvious about what these Windows 10 updates actually address.
Transparency IS a good thing whether talking about Government or OS.
I think a large part of consumers uneasiness about Windows 10, especially power users, but I know of PLENTY of
ordinary users that know enough want to see things explained. Honestly Microsoft hurts themselves because of
being closed mouth.
yeah I just don't see how a serious business would want Windows 10 on their machines with its mobile look and live tiles. Although I guess it's better than 8/8.1, I skipped right over that abomination. I couldn't believe they tried to force that metro screen over the traditional desktop.
Cumulative updates are always an adventure. I'll spend the next few days waiting for the settings changes to reveal themselves. Why do they always have to reset some settings back to Microsoft preferences? I think I must build a checklist of settings to check after an update, but even then I'd expect to be surprised.
Just FYI, checked the SFC /SCANNOW on the .71 image and it still finds errors on opencl.dll as in earlier Builds/cumulative updates (the latest Tech Preview, however, has fixed this issue). A new file has joined the mix in CBS.log: profapi.dll. From what I can find online, this item seems to be browser related, possibly Chrome or Firefox. Very interesting... because DISM /Online /Cleanup-Image /CheckHealth still returns "No component store corruption detected." I guess this will be fixed when the Redstone family of releases gets to the current branch, at the latest -- hopefully, earlier than that!
--Ed--
As far as the Opencl.dll problem, the ONLY way to see if it has been fixed, by MS is to run SFC /Scannow as this command is what removes one, and replaces the other with the one from MS. I don't believe this has been fixed by MS yet.
Updated: didn't see the post from EDTittel before I posted this....my bad.