Saturday 18 November 2017

Posts from Pete's PC Repairs on Facebook




View this in your browser

Pete's PC Repairs on Facebook

Facebook feed

Excerpts:

Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans




Patch Tuesday toll: more than 1,100 separate patches, but nothing critical for Windows. We're seeing many bugs. None have elicited more vituperation than the forced upgrade to Fall Creators Update, ignoring the "CBB" setting in 1703. Perhaps it's not a bug but a feature? 



7 Reliable Sites To Do A Quick Free Anti-Virus Scan






2018 Is Likely To Be A Worse Year For Ransomware Than 2017

2018 Is Likely To Be A Worse Year For Ransomware Than 2017 


2018 Is Likely To Be A Worse Year For Ransomware Than 2017 


Pete's PC Repairs, your local, affordable solution for all you home or business IT...

Pete's PC Repairs, your local, affordable solution for all you home or business IT needs http://petercraine.wixsite.com/petespcrepairs Don't Despair we Repair 





we are now closed for the day, see you soon, for out of hours support please contact us through our...

we are now closed for the day, see you soon, for out of hours support please contact us through our face book page.https://facebook.com/petespcrepairsblackburn/?business_id=1931743440399760 





Copyright © 2017 Pete's PC Repairs, All rights reserved.

pesky windows updates

Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 1 of 8
WOODY ON WINDOWS
By Woody Leonhard, Columnist, Computerworld
NOV 15, 2017 10:52 AM PT
NEWS ANALYSIS
Microsoft forces Win10 1703 customers onto 1709, and other Patch
Tuesday shenanigans
Patch Tuesday toll: more than 1,100 separate patches, but nothing critical for Windows.
We’re seeing many bugs. None have elicited more vituperation than the forced upgrade to
Fall Creators Update, ignoring the “CBB” setting in 1703. Perhaps it’s not a bug but a
feature?
Another massive outpouring of Microsoft patches yesterday — more than 1,100
separate patches — brought a few surprises and shouts of indignation from a
forced but unannounced upgrade. Some bugs are already evident, and there’s
a storm brewing over one Office patch. But by and large, if you don’t use
Internet Explorer or Edge, it’s a non-event.
Every version of Windows got patched yesterday (Win10 1709, Win10 1703,
Win10 1607, Win10 1511 Enterprise, Win10 1507 LTSC, Win 8.1, Win RT 8.1, Win
7, plus Server 2016, 2012 R2, 2012, 2008 R2, 2008). Almost every version of
Office (2016, 2013, 2010, 2007, plus 2013 and 2010 Click-to-Run). Plenty of
miscellaneous, too: IE 11, 10, 9 and Edge, Flash for all, SharePoint Server, the
ChakraCore package, and various .Nets including ASP.NET. The good news?
Unless you use IE or Edge, there’s nothing pressing — you can sit back and
watch the bugs crawling out of the woodwork.
Martin Brinkman at ghacks has a spreadsheet you can download if you’re
curious. He shows more than 1,100 separately identified patches.
! Sign In | Register"
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 2 of 8
All of that’s in addition to the 43 non-security Office patches released last
week, the Win7 and 8.1 Security-only patches, and the Monthly Patch
previews.
Behind the curtain
For most of you, the key patches are these:
Win10 1709 KB 4048955 Build 16299.64
Win10 1703 KB 4048954 Build 15063.726 (and 15063.728?)
Win10 1607 KB 4048953 Build 14393.1884 - there's also an entry for
KB4051033 , Build 14393.1913, but there's no KB article, and no indication
what it's for.
Win10 1511 Enterprise and Education only KB 4048952 Build
10586.1232. Note that this cumulative update does not install on Home or
Pro versions (thx, @teroalhonen)
Win10 1507 LTSC only KB 4048956 Build 10240.17673
Win 8.1 KB 4048958 2017-11 Monthly Rollup
Win 7 KB 4048957 2017-11 Monthly Rollup
There’s a handful of fully disclosed bugs in the patches. You can see them in
the KB articles associated with the individual patches. For the Win10 patches:
Internet Explorer 11 users who use SQL Server Reporting Services (SSRS)
may not be able to scroll through a dropdown menu using the scroll bar.
(Fix: Change the document mode.)
Universal Windows Platform (UWP) applications that use JavaScript and
asm.js may stop working. (Fix: Uninstall, then reinstall the application.)
May change Czech and Arabic languages to English for Microsoft Edge
and other applications. (Fix: We’re working on it.)
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 3 of 8
But of course the disclosed bugs are never as interesting — or as problematic
— as the unexpected ones.
[ To comment on this story, visit Computerworld's Facebook page. ]
According to Microsoft, four of the fixed holes have been publicly disclosed,
but none of them are being exploited in the wild at this point (which is to say,
they’re not zero-days):
CVE-2017-8700 — ASP.NET Core Information Disclosure Vulnerability
CVE-2017-11827 — Microsoft Browser Memory Corruption Vulnerability
CVE-2017-11848 — Internet Explorer Information Disclosure Vulnerability
CVE-2017-11883 — ASP.NET Core Denial of Service Vulnerability
Once again, you can see security holes in IE 11 inherited by Edge.
Adobe released 9 security bulletins and advisories, which fixed 86 individually
recognized security holes in Flash, Acrobat, Reader and other Adobe products.
As usual, Microsoft incorporated the Flash fixes into its Win 8.1, 8.1 RT, Win 10
and Server 2012, 2012 R2 and 2016 patches.
My long-standing advice still rings true: If at all possible, get rid of Flash and
Reader and use any browser other than IE or Edge.
Forced upgrade to 1709
The most vexing issue to crop up so far: Win10 Pro users who have their Group
Policy set to block upgrades from 1703 (Creators Update) to 1709 (Fall Creators
Update) are getting pushed onto 1709. Win10 1703 Pro users set to hold off for
"Current Branch for Business" got bushwhacked, too. Poster NetDef on
AskWoody says:
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 4 of 8
All (and I mean ALL) 1703 systems today, even with correct Group Policy
settings enforced, that were NOT under a WSUS system have picked up and
installed (or attempted to install) the 1709 feature update.
Test systems that had CBB set, but also had the defer updates set for 60 or
more days, did NOT update today.
Test systems where we used WUShowHide to hide/defer the 1709 update
have ALSO attempted to upgrade to 1709 today.
MS has apparently greatly shorted the wait time for (formerly known as
CBB) from 4 months to 1 month. I do not yet know if this was an accident,
or intentional.
Given all of the recent complaints about bugs in the Fall Creators Update,
being forced onto 1709 even with the “Current Branch for Business” set in the
Security & Updates Advanced Options (screenshot) is unconscionable.
Microsoft has retroactively redefined “Current Branch for Business” — which is
to say, it has eliminated it — without warning, and without allowing customers
to change their settings to something that says, in effect, back off.
Woody Leonhard/IDG
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 5 of 8
Poster @MrBrian echoes the damnation of many:
My educated guess is that this was not an accident. The “Microsoft
recommends” tag on the official Win10 release information site now points
to 1709. Microsoft is now purposely blurring the distinction between what
was formerly Current Branch and Current Branch for Business. I’m not
surprised that Microsoft did this, but I would have thought that Microsoft
would have given prominent notice beforehand (or did they?)
The only solution at this point is to make sure you have the feature update
deferral setting ratcheted all the way up to 365 days. See my recommendation
from October. If you got upgraded and don’t want to join Microsoft’s unpaid
beta-testing club for 1709, you can roll back using Start > Settings > Update &
security > Recovery and under “Go back to the previous version of Windows
10” click Get Started. Provided you roll back within 10 days, you should end up
with your old system.
Problems on the Office front
Catalin Cimpanu at BleepingComputer calls out a worrying Excel patch, CVE-
2017-11877 - Microsoft Excel Security Feature Bypass Vulnerability —
previously undisclosed, that may allow jimmied Excel worksheets to bypass the
usual auto-execution restrictions. No known exploits, as yet, but it’s unnerving.
There’s a new security advisory, ADV170020 - Microsoft Office Defense in
Depth Update, that has exactly no description. Dustin Childs at Zero Day
Initiative offers this possible explanation:
If one were to guess, it’s likely this advisory is related to the recent spate of
malware abusing the Dynamic Data Exchange (DDE) protocol. DDE
provides data exchanges between Office and other Windows applications,
however attackers leverage DDE fields to create documents that load
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 6 of 8
malicious resources from an external server. Microsoft claims attackers may
be abusing the feature, but it’s not a vulnerability per se. Hopefully, the
update provided by this advisory restricts the abuse of this “feature” in some
manner.
I talked about the suddenly popular {DDEAUTO} field on AskWoody last week
in response to Microsoft’s Security Advisory 4053440. It looks like the
mysterious ADV170020 somehow automates a subset of the manual tweaks
provided in SA 4053440 but, of course, Microsoft has provided zero
documentation. Security by obscurity, eh?
It also appears as if the new fixes for the “Unexpected error from external
database driver” bugs are working. You may recall that those buggy patches for
the buggy patches — KB 4052233, 4052234, and 4052235 — were pulled and
completely obliterated from the record late last month. This month, we’re
seeing fixes for all versions of Windows, including 1709 with this reassuring
note:
Addressed issue where applications based on the Microsoft JET Database
Engine (Microsoft Access 2007 and older or non-Microsoft applications) fail
when creating or opening Microsoft Excel .xls files. The error message is:
“Unexpected error from external database driver (1). (Microsoft JET
Database Engine)".
More of a mixed bag
There’s some good news. @abbodi86 confirms that Microsoft fixed the
retrograde bug I reported last month in the 2017-11 Win7 Monthly Rollup
Preview, the SFC scanning bug that originated long ago in KB 3125574.
And there are some odd glitches:
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 7 of 8
Win7 Pro may get a Malicious Software Removal Tool update that’s
marked “important” but not checked for installation (thx, @alpha128).
Win10 1709 may get an MSRT update that’s incorrectly marked “for
Windows Insider Preview” (thx Joh582n).
The service “Microsoft .Net Framework NGEN v4.0.30319_X86” may no
longer start automatically.
Outlook 2016 Click-to-Run version 1710 build 8625.2121 clobbers the
View Settings button (acknowledged bug with a half-fast workaround).
Excel 2013 and 2016 may get a cursor flicker after updating to 1709
(acknowledged bug).
Equation Editor phunnies
Finally, the most contentious patch of all. The Embedi malware folks found a
severe security bug in the old — 17 years old — Office Equation Editor. You may
remember the Word Equation Editor, which about 10 people once used to
make equations look nice inside their Word docs. Almost everybody has the
Equation Editor installed and enabled. Almost everybody with Office is
vulnerable. But there’s no hue and cry as yet because working exploit code
isn’t available. Yet.
Microsoft has a writeup for the security hole CVE-2017-11882 - Microsoft
Office Memory Corruption Vulnerability. Microsoft lists it as “Important -
Exploitation less likely” with no known exploit code.
Embedi insists that the problem can be triggered with no user prompt.
Microsoft, by virtue of its “Important” designation, claims that some user
intervention is required. Embedi says it has exploit code, which it delivered to
Microsoft on March 8. Microsoft says it has no functioning exploit code.
Microsoft forces Win10 1703 customers onto 1709, and other Patch Tuesday shenanigans | Computerworld 18/11/2017, 08)50
https://www.computerworld.com/article/3237172/microsoft-windows/…03-customers-onto-1709-and-other-patch-tuesday-shenanigans.html Page 8 of 8
Copyright © 2017 IDG Communications, Inc.
YOU MIGHT LIKE
SHOP TECH PRODUCTS AT AMAZON
Who’s right? Who knows? You can manually circumvent the problem by
making two registry changes listed in the Embedi article.
It’s a messy month. With no “critical” Windows updates, as long as you don’t
use IE or Edge, there’s no huge pressure to apply the updates just yet.
Thanks to @GossiTheDog, @teralhonen, @barbbowman, @abbodi86,
@PKCano, @MrBrian, and the many intrepid testers on AskWoody.
Hit a bug? We’re all ears on the AskWoody Lounge.
Windows Hello for Business: Next-gen authentication for Windows shops
Follow # ✉ ! " #
Woody Leonhard is a columnist at Computerworld and author of dozens of Windows books, including

"Windows 10 All-in-One for Dummies."

Saturday 11 November 2017

New Service goes live on Sunday



As revealed last month - tomorrow (Sunday) is the launch day for the new service, availability is limited, so you are going to want to get in quick, make sure you check back regularly, bookmark us and don't forget to like and follow the page !!!

Peace of mind Guaranteed



How would you like to take all the worry out of owning a computer, all your concerns about viruses, malware, ransomeware and the general health of your computer. Look no further for only £7 per month, yes thats right only £7 per month (but only for the first 30 people) you can have a fully monitored, updated and protected computer.





Heres what you get



  • Fully Managed and Monitored Antivirus and Malware protection (daily updates, monitored alerts, permission led outcomes)
  • Fully Managed and Monitored Anti-ransomeware, keeping you safe from fast emerging threats
  • Remote Support (no need to plan and arrange an
    appointment get near instant support (subject to availability and fair use policy))
  • Fully Monitored computer, alerting you to any potential problems leading to access to :-
  • Your own personal supportdesk to report any problems you may have
  • Annual Computer MOT (drop off and pickup service available)


Optional Extras (ask for price)



  • Data Backup
  • Computer Backup
  • Out of Hours support
  • Priority Customer Support
  • Health Check



Goto Facebook to book you computer in for this offer
Only available to the first 30 people to book - after that full price will be payable