Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • The Reg: Windows 10 source code leaked

    Posted on June 23rd, 2017 at 17:04 woody Comment on the AskWoody Lounge

    Chris Williams at The Register reports that 32TB of Win10 internal builds, including some source code for core processes, is available for download.

    The leaked code is Microsoft’s Shared Source Kit: according to people who have seen its contents, it includes the source to the base Windows 10 hardware drivers plus Redmond’s PnP code, its USB and Wi-Fi stacks, its storage drivers, and ARM-specific OneCore kernel code.

    I searched betaarchive.com and couldn’t come up with a link to the goodies, so I won’t vouch for the veracity of the claim, but it’s certainly provocative. The search continues.

    Leaked Shared Source Kit ain’t the end of the world, but it certainly would make the search for exploitable bugs a whole lot easier.

    UPDATE: the Reg is backpedaling. There’s a reason why I couldn’t find the code on betaarchive – they’ve removed some of it. The Reg article has been updated

    In a statement, Beta Archive said: “The ‘Shared Source Kit’ folder did exist on the FTP until [The Register’s] article came to light. We have removed it from our FTP and listings pending further review just in case we missed something in our initial release. We currently have no plans to restore it until a full review of its contents is carried out and it is deemed acceptable under our rules.”

    Translation: some smoke, no 🔥

  • Windows 10 beta build 16215 rolls out…

    Posted on June 8th, 2017 at 19:37 woody Comment on the AskWoody Lounge

    … and it’s huge.

    The official tally includes:

    New user interface for Start and the Notification center

    A few Edge improvements that slowly bring the feature set in line with IE: pinning web sites on the taskbar, full screen mode, EPUB improvements (yawn) and very minor PDF improvements.

    Cortana now looks into your camera roll and, optionally, creates reminders. You can also use the pen to scrape reminder info off web pages.

    Handwriting improvements. You can use the pen to scroll. Easier emojis. Dictation on the desktop. And much more.

  • Windows 10 Pro for Workstation PCs/Advanced PCs?

    Posted on June 5th, 2017 at 00:48 woody Comment on the AskWoody Lounge

    If you haven’t been following along with the latest Windows 10 rumors, here’s another unexpected twist:

    “Introducing Windows 10 Pro for Workstation PCs.”

    No idea if it’ll appear in the Fall Creators Update timeframe…

    More details from Pradeep at MSPower User.

    Paul Thurrott nails it:

    Windows 10 isn’t a growth machine, it’s a legacy business that needs to be made simpler, not more complex, in order to slow the decline. Adding product editions now simply reminds customers how out of touch this strategy is with today’s mobile first, cloud first world. And this will hasten, not slow, the move away from traditional PCs. In other words, don’t defend the indefensible. This is stupid. Period.

    +1

  • Windows file History to disappear in the Fall Creators Update?

    Posted on June 5th, 2017 at 00:31 woody Comment on the AskWoody Lounge

    There’s a lot of speculation on the web about the future of the Windows File History feature.

    You may recall that Windows 8’s File History replaced Windows 7’s “Previous version” shadow copy capability. Both maintain backup copies of user files stored in common locations. It was one of the big selling points for Windows 8 — as I described in InfoWorld five years ago:

    (In Windows 8), Microsoft is finally catching up with Apple’s Time Machine by introducing a very straightforward file backup feature called File History, found in Control Panel.

    Ends up that the mistakenly-pushed build 16212 of Windows 10 doesn’t include File History. The peripatetic Walking Cat found a telltale character string in one of the build 16212 system files:

    “Making new backups with File History is no longer supported.”

    You can read that a lot of ways, and there’s always a chance that it won’t appear in the final version of the Fall Creators Update, expected in September of this year. But it would be characteristic of Microsoft’s push to get your data into their cloud.

    Paul Thurrott has an excellent outline on Thurrott.com of the arguments in favor of dumping File History, with one key argument: If you’re updating a file from two different computers, the “latest” version won’t synch correctly.

    Microsoft may use that as a reason to get you to use OneDrive. Then again, they may have a more complex — and compelling — argument by the time Fall Creators Update arrives. Or it may be a phantom harbinger of the next, next version of Windows 10.

    Personally, it won’t make much difference for me. I have all of my important files in Dropbox and use it religiously, with occasional manual backups in OneDrive. I’m still amazed at how easy it is to grab a laptop (or phone) and go on the road, with all of my files — going back many years — sitting there, waiting for me, no matter which OS I’m using on what computer.

  • Win10 upgrades are still free

    Posted on May 29th, 2017 at 18:15 woody Comment on the AskWoody Lounge

    Ed Bott says so – and he should know.

    If you have a machine with a valid Win7 or 8.1 license, the upgrade to Win10 continues to be free, just as I described a year ago. Nod, nod, wink, wink.

    It’s in Microsoft’s best interests to get you into the Win10 groove.

  • Not all Windows Store apps will run on Windows 10 S

    Posted on May 19th, 2017 at 07:43 woody Comment on the AskWoody Lounge

    From ‘Softie Rich Turner, on the MSDN forum:

    Just because an “app” comes from the Windows Store does NOT automatically mean that it’s safe & suitable for running in Windows 10 S. There are some apps that are not allowed to run on Windows 10 S, including all command-line apps, shells and Consoles.

    That’s news to me. I bet it is to you, too.

    Thx, @teroalhonen.

  • Windows 10 on ARM

    Posted on May 11th, 2017 at 16:05 woody Comment on the AskWoody Lounge

    Looks like we’re going to see Windows 10 running on Snapdragon chips by the end of the year.

    This is a fascinating presentation:

    https://channel9.msdn.com/Events/Build/2017/P4171

    Windows 10 on Snapdragon/ARM chips will run Win32 apps through a “X86 Win32 emulation layer,” which is surprisingly fast. Watch at the five minute mark forward.

  • Google Chrome won’t be allowed on Windows 10 S

    Posted on May 10th, 2017 at 05:05 woody Comment on the AskWoody Lounge

    If you haven’t read Ed Bott’s latest ZDNet article, and you’re even remotely interested in Win10 S, hurry over there and absorb it.

    The approach — forcing browser makers to use the native plumbing — isn’t new. Apple requires iOS browsers to use WebKit, for example (see Paul Krill’s article). We saw something similar with the IE-as-default wars in Windows 8.

    Microsoft’s between a rock and a hard place, but the decision doesn’t surprise me at all. What does surprise me is that it’s laid out in black and white. I expected to see months of waffling.

    In my opinion, keeping Chrome off Win10 S is just another nail in Win10 S’s coffin. But it really couldn’t be any other way.