Posted on 03/16/2017 10:02:00 AM PDT by upchuck
Microsoft's forthcoming Creators Update offers a mixed bag of fixes for Win10's biggest knocks
Windows 10 will get better in the forthcoming Creators Update. That isnt a hollow promise or more marketing drivel. Its a straightforward observation, comparing the most egregious parts of the current version, Win10 1607 Anniversary Update, with near-final betas of the next version, 1703. While its too early to gauge 1703s stability, the feature improvements are very real.
Windows 10 beta build 15031, which appeared on Feb. 8, was the first Win10 build in the rs2_release branch. Thats the point where a fork in the Win10 beta process started honing in on the final release of Windows 10 Version 1703, the Creators Update. The last major change weve seen came in build 15042, on Feb. 24, with the unveiling of a new disappearing Pause Updates pane in the Settings app. Since that point the changes have been largely cosmetic, with bug fixes taking center stage. [ The essentials for Windows 10 installation: Download the Windows 10 Installation Superguide today. | Stay up on key Microsoft technologies with the Windows Report newsletter. ]
Of course well be talking about the Creators Update in the coming weeks and months as the bugs get ironed out. But theres a big picture lurking thats crucial for many admins, Win10 owners, and Win10 maybe-wannabes.
As Eric Knorr notes in Which Windows 10 should your business install?, if youre thinking of moving to Windows 10, nows the time to do it. The current version, the 1607 Anniversary Update, is the most stable and obvious choice, and it will remain so for many months. But real improvements lurk in 1703. You should know about them.
Here are the five complaints about Windows 10 Anniversary Update 1607 that I hear most often. Lets take a look at how things stand now and how Windows will evolve in 1703. Keep in mind that 1703 wont be business ready when its first available (likely in May). If you need Windows to work all the time, its much smarter to wait until 1703 matures sufficiently to enter prime time (what Microsoft calls Current Branch for Business), which will likely occur in August or September.
Read entire article, fairly long, here.
Thank you. Excellent adjustment.
I vaguely recall reading about this problem. Seems like there was a fix or a workaround. Might do some searching.
Yeah, ok... [/eyeroll]
My Windows-7 computer went down and I'm presently using one with Windows-8.1....I'm surprised, I like it.
My computer repair guy bookmarked this onto my computer: Never Ten
I've never used it or even looked at it real close.
Amen. These days you can’t trust any operating system with Obama’s CIA goons lurking around cyberspace.
You are free to compile the Linux kernel after carefully examining the code....
Only downside to Win 7 is it sunsets in Jan 2020.
You literally can’t ignore Apple updates. At some point they’re forced to your phone. Microsoft is not the only game in town requiring this.
I have 5 computers on Windows 10, they all work great. I hated Windows 8, however.
Nope.
Hell no,
Just built two new i7 boxes running win7 x64.
There are more of us using Win 7 than you know. We have it on business computers linked to the internet. Have one computer with XP not connected to the internet that we keep all our client, patient demographics, financial info and software we use daily which we have had since 1985. Works fine. If forced to upgrade to W10, told my clients I’m retiring.
Sheesh...ever since the new updates arrived, this ( Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429) - Error 0x80073701) will not install and I am having kernal data in page errors when my computer starts.
Cortana...I can’t stand it. It seems like such a hog!
I like Win7, and continue to use it for the most part, both at home and at work (at home I still have an XP system as well.)
But while I use Win7 at work as my primary desktop, I've had to get a Windows 10 laptop, since there's a lot of the newer Microsoft products (Office 365, Exchange 2016/Online, and others) that can't be properly administered from any OS older than Windows 8.1. Even some admin functions delivered through web sites don't work properly on Windows 7 workstations. And don't even get me started on PowerShell on Windows 7, where many of the modules simply won't work, even when I've upgraded to PowerShell 4!
Mark
I don’t think they know what the word “fatal” means.
Be sure to carefully examine the C compiler code and make scripts beforehand, to protect against back-door insertion like the classic back-door inserted into Unix by Ken Thompson - The C compiler checked for the presence of a back door, and if the code had been removed, the compiler would re-insert the code before the compilation process (this is an over-simplification of what Ken did - It was really brilliant!)
Put simply, if you removed his back-door, the act of recompiling the code would re-insert it without you realizing it.
Mark
You're not alone by a long shot. I will never switch over to Windows 10. Hell, the U.S. government and many major industries are still using Windows XP.
https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf
Above is the “Trusting Trust” paper. He proves no code that you don’t create from scratch, including the compiler to build it, can’t be trusted. At some point, we have to use software we can not truly trust.
I’m so darned confused. :-)
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.