Patch Lady Posts – Windows 7 and the SCARD_E_NO_SERVICE error

Topic

New Reply

Woody wrote ….”There’s a new bug posted for KB 4074598, the February Win7 Monthly Rollup, and KB 4074587, the Feb Win7 Security-Only patch, that tri
[See the full post at: Patch Lady Posts – Windows 7 and the SCARD_E_NO_SERVICE error]

Susan Bradley Patch Lady/Prudent patcher

7 users thanked author for this post.

walker, JDeC, WildBill, Pepsiboy, OscarCP, Elly, woody

Reply | Quote

Replies

I just got this question from Vess Bontchev:

https://twitter.com/VessOnSecurity/status/969135002809262080

Is it really safe to delete the contents of the CBS folder? Is it not used for anything? My disk is far from full but there are about 10 Gb of files there, which I’d rather reclaim if they aren’t needed.

Is it safe to delete all of the CBS folder?

Reply | Quote

Yes, the files will be recreated during TrustedInstaller.exe and TiWorker.exe in post Windows 7 World runs.
Probably leaving the folder empty as placeholder is the safest.

5 users thanked author for this post.

AJNorth, SueW, woody, Pepsiboy, FakeNinja

Reply | Quote

I told Vess. Thanks!

Wish there were some way to get him to join us on AskWoody. Brilliant guy, experienced, no bull.

Reply | Quote

I keep the most recent cbs.log file just because if I need to dig into what is going on with the cbs (ooooh blog post idea) I have the most recent one, but I nuke all the old ones.

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

AJNorth, Cascadian, pkoryn

Reply | Quote

Again, yes. It is completely safe to do so, so long as you do not delete the CBS folder itself. I will add one caveat. As we all know, Windows 7 is not entirely stable after reboot until Windows 7 has been running for at least 10 minutes AFTER YOU LOG INTO WINDOWS. Windows 7 is considered to be “booted and up and running” when the login screen appears, yet Windows is NOT fully booted until 10 minutes AFTER the user logs into Windows 7, since stuff under the user’s account still had to be run.

With the above in mind, any Windows 7 user can wait 10 minutes AFTER logging into Windows 7 and then delete all of the contents within the CBS folder, and then reboot the computer. On reboot, Windows will merrily create new log files within the CBS folder after reboot. Upon reboot and after waiting 10 minutes after logging into Windows 7, the user can then examine the new log files which were created within the CBS folder since the creation of these new log files will have been completed.

1 user thanked author for this post.

SueW

Reply | Quote

? says:

hey, i’m no win guru, however; after every monthly update cycle i delete the CBS file when cleaning with DISM, that is if makecab doesn’t get to it before i do. usually 60MB or there abouts. personally i leave the “Persist” files as they are. they seem to cycle without complaining…

Reply | Quote

Patch Lady, and also others who might be in my situation,

I do not use a card to log in, but working through government contracts and doing a lot of telecommuting, I cannot fail to notice a strong tendency for access to a government computer from home getting progressively more restricted. At present, having a car reader and a card with a chip in it to login is an option to doing it with token+PIN, which I can do using the PC’s keyboard. But who knows what the future holds? So I’ll wait a bit, to see if MS puts out a fixed February security only update before too long. Otherwise, with the current one installed, I might have problems if one day, maybe a year or more from now, it turns out that I need to get myself that card reader and smart card, but by then I’ll have forgotten all about the leaking handle problem…

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

Fixed in another preview rollup
https://support.microsoft.com/en-us/help/4091290/march-1-2018-kb4091290

4 users thanked author for this post.

AJNorth, GoneToPlaid, MrBrian, walker

Reply | Quote

abbodi86 wrote:

Fixed in another preview rollup https://support.microsoft.com/en-us/help/4091290/march-1-2018-kb4091290

!!! Yep and Group B DO NOT INSTALL !!!

Satya is trying to trick you into installing a full, unwanted spyware loaded Rollup that has been deliberately mis-named and falsely described on Windows and/or Microsoft Update and the Update Catalog to appear as “just” an “Update for Windows 7” that “just” fixes the SCARD_E_NO_SERVICE error issue.

Viper

1 user thanked author for this post.

JDeC

Reply | Quote

This is concerning. How did you find out that the patch isn’t quite what it’s said to be?

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

Yep! You beat me too it. A rollup. They better do a Security Only replacement for kb4074587 then!!!

2 users thanked author for this post.

OscarCP, JDeC

Reply | Quote

This is a fix for those enterprises who do use smart cards.  If you want to not install the cumulative update model just stick to security only since I’m going to guess that most in this thread do not use smart cards.  Telemetry is not spyware, there is a vast difference.  Businesses use “big data” to give them better views of what their customers use.

This isn’t a trick, Microsoft tends to put the fixes for bugs into non-security patches.

Reply | Quote

Thanks for the warning. I’m Group B and avoid systematically to install anything with “preview” or “rollup” in the name, except for the”E11 security only cumulative rollup”, as this is the only update for E11 I know of with “security only” in the name.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

anonymous wrote:

? says: hey, i’m no win guru, however; after every monthly update cycle i delete the CBS file when cleaning with DISM, that is if makecab doesn’t get to it before i do. usually 60MB or there abouts. personally i leave the “Persist” files as they are. they seem to cycle without complaining…

You can blow out the persist files as well. Read my post about waiting 10 minutes after actually logging into Windows 7 before blowing out the entire contents of the CBS folder.

Reply | Quote

? says:

thank you GTP! the waiting is the hardest part…

I’m a MOG!

now if i could only find PA Bear to find out what is up with this infernal empty MSE telemetry folder in %temp%

Reply | Quote

I do regret being the one to inform you. Please see this topic. I am glad you found PA Bear a helpful voice. His depth of knowledge was among the highest. But it was his true troubleshooter’s logic flow that demanded a proper list of symptoms before beginning that stood out from others. This is what solved many of the misunderstandings, for those with patience.

Wanted to leave this, for others who may not have been informed.

1 user thanked author for this post.

SueW

Reply | Quote

? says:

thank you “Cascadian” PA Bear was always on it, especially with MSE type problems. between him and Stephen Boots they were my go to guys before the lounge kicked in. Microsoft security products have always been hard for me to decipher, started with “One Care” when my ISP included it with the subscription. side note the MSE updated properly this am, no double update stuff.

this link may be of interest, PA Bear’s helpful comment is at the top of page 2

https://answers.microsoft.com/en-us/protect/forum/mse-protect_scanning/does-mse-have-the-ability-to-scan-from-the-command/809b0b84-9396-49b2-95c4-68e7ec539fc7

Reply | Quote

ViperJohn wrote:

abbodi86 wrote:

Fixed in another preview rollup https://support.microsoft.com/en-us/help/4091290/march-1-2018-kb4091290

!!! Yep and Group B DO NOT INSTALL !!! Satya is trying to trick you into installing a full, unwanted spyware loaded Rollup that has been deliberately mis-named and falsely described on Windows and/or Microsoft Update and the Update Catalog to appear as “just” an “Update for Windows 7” that “just” fixes the SCARD_E_NO_SERVICE error issue. Viper

Thank you for the info. This of course is not surprising at all. Hmm…Think about how Microsoft has renamed the functionality for KB2952664 after, what was it???, around a month or so ago I posted about the riot it was that, at the time, Microsoft was still claiming that KB2952664 was for upgrading to Windows 10 when in fact KB2952664’s only real function was to install telemetry? Perhaps I made Microsoft’s lawyers scratch their heads?

The upshot is, that the more we all remain diligent, then perhaps the more influence we all might have in putting an end to Nadella treating all of us as his beta testers and as his unwitting slaves for tracking absolutely everything which we do, WITH OUR PERSONAL COMPUTERS AND FOR WHICH NO SUBSEQUENT EULAS FOR DEEP SYSTEM WIDE TELEMETRY WERE EVER PRESENTED BY MICROSOFT FOR WINDOWS UPDATES WHICH INSTALLED SAID TELEMETRY. Microsoft’s assumption is that if you download and install their updates, then you have consented, by the act of downloading and installing the updates, to their embedded telemetry. This is really putting the cart before the horse, yet it is what it is, since you chose to install their updates. And this is what Microsoft’s attorneys will argue in court, six ways from Sunday.

2 users thanked author for this post.

JDeC, SueW

Reply | Quote

1. February 13, 2018—KB4074587 (Security-only update) no longer lists this issue.

2. March 13, 2018—KB4088875 (Monthly Rollup) does not list this issue, so I assume it includes the fix.

1 user thanked author for this post.

walker

Reply | Quote