{"id":10521,"date":"2017-11-17T06:30:36","date_gmt":"2017-11-17T14:30:36","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2017\/11\/17\/news-4293\/"},"modified":"2017-11-17T06:30:36","modified_gmt":"2017-11-17T14:30:36","slug":"news-4293","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2017\/11\/17\/news-4293\/","title":{"rendered":"Patch alert: Microsoft acknowledges printer bug; forced 1709 upgrades continue"},"content":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Fri, 17 Nov 2017 06:06:00 -0800<\/strong><\/p>\n

The patches have been out for only a few days, but as best I as can tell at this early juncture, November\u2019s Patch Tuesday bugs aren\u2019t as bad as they were in October<\/a>. Thank Redmond.<\/p>\n

If you use an Epson dot matrix printer, if you\u2019re seeing an error that CDPUserSvc has stopped working, or if you were forcibly upgraded from Win10 Creators Update, version 1703, to Fall Creators Update, version 1709, I have some good news and some bad news.<\/p>\n

Microsoft has acknowledged a bug in its Patch Tuesday updates that causes \u201csome Epson SIDM and Dot Matrix printers\u201d to fail. The bug appears in this month\u2019s patches for every<\/strong> <\/em>version of Windows:<\/p>\n

Microsoft doesn\u2019t acknowledge the bug in the Win 8.1 Security-only (manual download) patch, KB 4048961<\/a>, or in the Win 7 Security-only patch, KB 4048960<\/a>, but I\u2019ve seen reports that they\u2019re similarly afflicted.<\/p>\n

You have to wonder when Microsoft stopped testing dot matrix printers \u2014 and why this bug wasn\u2019t picked up in the numerous Monthly Rollup Previews.<\/p>\n

Microsoft says:<\/p>\n

After installing this update, some Epson SIDM and Dot Matrix printers cannot print on x86 and x64-based systems. … Microsoft and Epson have determined the cause of the issue and are working on a solution. This problem is not related to the printer driver, so installing current or older print drivers will not resolve the issue. Microsoft will provide an update in an upcoming release.<\/p>\n

Which is Microsoft-speak for \u201cthere\u2019s a bug in the patch, not in Epson\u2019s drivers, and we\u2019ll try to figure out a way to fix it as soon as we can.\u201d It\u2019ll be interesting to see if we get a silver-bullet patch \u2014 one patch that kills this specific buggy \u201csecurity\u201d behavior \u2014 or if we\u2019ll see a new out-of-band cumulative update, sooner or later.<\/p>\n

Until Microsoft gets its act together, the only solution is to uninstall the latest security patch and hide it so Windows won\u2019t install it again. While you\u2019re at it, consider whether<\/a> the gain from patching on Patch Tuesday outweighs the schadenfreude of watching others go down in flames.<\/p>\n

The problem that I described on Wednesday<\/a> continues apace: People all over the world who had set Win10 Creators Update to wait for \u201cCurrent Branch for Business\u201d before moving on to the next version are getting sandbagged. Windows Update is apparently turning a blind eye to the \u201cCBB\u201d setting. But, as explained on Wednesday, it does honor the \u201cfeature update deferral\u201d setting.<\/p>\n

No doubt somebody at Microsoft thinks that the setting can be ignored, now that the \u201cCBB\u201d terminology has been replaced with \u201cSemi-Annual Channel.\u201d Except, of course, the CBB terminology persists in Microsoft\u2019s own documentation<\/a>. Dirty pool.<\/p>\n

There\u2019s a new wrinkle. I have an unconfirmed report from Henk van Elburg<\/a> that some folks with Win10 1607 set to wait for CBB are also getting upgraded to 1709. Without permission, of course.<\/p>\n

A report from robincm2 on the TechNet forum<\/a> says that folks with Win10 Anniversary Update, version 1607, are seeing a notification about CDPUserSvc failing, every time they log on to Windows. Robincm2 goes on to provide this screenshot:<\/p>\n

Microsoft hasn\u2019t acknowledged the problem yet, but it seems to be associated with the Win10 1607 and Server 2016 patch KB 4048953<\/a>. G\u00fcnter Born talks about the error in his German-language Borns IT- und Windows-Blog<\/a>. In an unsigned piece, the Informa blog myITforum<\/a> goes on to say:<\/p>\n

According to reports, the CDPUserSvc (Connected Devices Platform Service) service stopped working for a few customers with October updates, but was then recognized as not working by a larger group after the November updates for Windows 10 were delivered this week. The issue only happens for Windows 10 1607 users. Microsoft support suggests the ultimate solution is to just upgrade to Windows 10 Fall Creators Update: This problem behavior is a known issue in RS1 and is tracked under Issue #8013247. This issue with the service has been fixed in RS2. And, according to the statement it doesn\u2019t seem likely that an ultimate fix will be proffered \u2014 except for upgrading. We\u2019ll have to wait to see how Microsoft ultimately handles the situation.<\/p>\n

Glenn Turner on the patchmanagement.org mailing list has put together a clever script<\/a> that disables the CDPSvc and CDPUserSvc services.<\/p>\n

My recommendation from last week<\/a> stands: Temporarily turn off Automatic Update and let\u2019s see what the beta testers turn up.<\/p>\n

Have a bug that\u2019s bugging you? Join the entomologists on the AskWoody Forum<\/a>.<\/em><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Fri, 17 Nov 2017 06:06:00 -0800<\/strong><\/p>\n

\n
\n

The patches have been out for only a few days, but as best I as can tell at this early juncture, November\u2019s Patch Tuesday bugs aren\u2019t as bad as they were in October<\/a>. Thank Redmond.<\/p>\n

If you use an Epson dot matrix printer, if you\u2019re seeing an error that CDPUserSvc has stopped working, or if you were forcibly upgraded from Win10 Creators Update, version 1703, to Fall Creators Update, version 1709, I have some good news and some bad news.<\/p>\n

Dot matrix dissed<\/strong><\/h2>\n

Microsoft has acknowledged a bug in its Patch Tuesday updates that causes \u201csome Epson SIDM and Dot Matrix printers\u201d to fail. The bug appears in this month\u2019s patches for every<\/strong> <\/em>version of Windows:<\/p>\n

To read this article in full, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[714,10761],"class_list":["post-10521","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-security","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/10521","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=10521"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/10521\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=10521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=10521"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=10521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}