Posted on February 7th, 2017 at 13:06 Comment on the AskWoody Lounge
Feb 2017 Office non-security patches: 10 for Office 2013, 16 for Office 2016
The 26 patches are just starting to roll out the Update chute
This, being the first Tuesday of February, is designated “Office non-security patch” day. We’re just starting to see the patches appear.
For Office 2016
Update for Microsoft Office 2016 (KB3141504)
Update for Skype for Business 2016 (KB3141501)
Update for Microsoft Office 2016 (KB3114389)
Update for Microsoft Office 2016 (KB3141508)
Update for Microsoft Office 2016 (KB3127991)
Update for Microsoft Office 2016 (KB3141510)
Update for Microsoft Office 2016 (KB3141513)
Update for Microsoft Office 2016 (KB3141505)
Update for Microsoft Office 2016 (KB3128048)
Update for Microsoft OneNote 2016 (KB3141512)
Update for Microsoft Office 2016 (KB3128052)
Update for Microsoft Outlook 2016 (KB3141511)
Update for Microsoft PowerPoint 2016 (KB3128051)
Update for Microsoft Project 2016 (KB3141514)
Update for Microsoft Office 2016 (KB3141509)
Update for Microsoft Visio 2016 (KB3141500)
For Office 2013
Update for Skype for Business 2015 (KB3161988)
Update for Microsoft Office 2013 (KB3115489)
Update for Microsoft Office 2013 (KB3141491)
Update for Microsoft Office 2013 (KB3127966)
Update for Microsoft OneNote 2013 (KB3141494)
Update for Microsoft Office 2013 (KB3127972)
Update for Microsoft Outlook 2013 (KB3141495)
Update for Microsoft PowerPoint 2013 (KB3141461)
Update for Microsoft Project 2013 (KB3141499)
Update for Microsoft Visio 2013 (KB3141492)
Oddly, the TechNet Office Updates release note says they were released “on the Download Center and Microsoft Update” yesterday, Feb. 6, but I haven’t seen any reports of the patches being available until today.
No word on when the patches will get rolled into the most recent Click-to-Run release.
It’s much too early to tell if there are problems with any of them, but a spot check reveals that the KB articles have been posted, and they’ve been updated for February 7, 2017. Of course, I recommend that you hold off installing them until the dust has settled.
Thanks to PKCano!
Posted on February 7th, 2017 at 05:29 Comment on the AskWoody Lounge
Kevin Parrish at Digital Trends kicked Windows 10 Cloud around a bit, and came up with some surprising discoveries.
WinCloud, you may recall, is the internal name of the supposed “next” version of Windows. It was leaked on a Russian site over the weekend, and took the Windows blogosphere by storm, with lots and lots of contradictory rumors and guesses.
Microsoft’s mum, of course, so we don’t have anything but an obviously pre-pre-release version of Windows 10 that runs on Intel machines.
Parrish found a half-dozen features/settings that merit consideration, including the ability to install apps from anywhere (not just the Windows Store), and a test run of a converted Win32 app. There’s a list of very small differences between the current Win10 beta (15025) and this Windows Cloud beta. (One of the differences listed isn’t, in fact, a difference: Windows PowerShell will replace Command Prompt in the 1703 Power Menu.)
If you’re curious about the way Windows may be headed late this year, take a look.
UPDATE: WalkingCat, @h0x0d on Twitter, has just tweeted a retraction of sorts. It seems that the ability to restrict apps to Windows Store only is present in all editions of 1703. I can confirm that the setting is on my plain-vanilla copies of Win10 beta 15025.
Where does that leave us? With a functional test run of a Desktop App Converter/project Centennial-converted app – and a Cloud version that’s more enigmatic than ever.
ANOTHER UPDATE: Interesting conjecture on Twitter about Win10 Cloud’s positioning in the market.