Page tree
Viewable by the world
Skip to end of metadata
Go to start of metadata

 

Problem

Microsoft recently announced that Windows devices may fail to boot after installing Windows 10 Updates that were released on October 10 2017. This is the result of a problem on Microsoft's end in publishing the updates with IDs KB4041676 and  KB4041691. Microsoft has since revoked these updates, and has provided solutions for affected systems, as detailed below. Functional versions of these patches have since been released. It is estimated that as many as 265 Windows 10 systems running at Berkeley Lab may be impacted. These systems were identified because they have BigFix installed.

If you received an email from IT User Support about this issue, then your system has the potential to be affected. Even if your system appears to be working fine, there is a possibility that your system will fail to boot upon your next restart. 

Note that applying the Microsoft-recommended fix for this issue will require advanced Windows skills, and is best done by an IT professional. You can either apply one of the solutions listed below or contact the IT Help Desk by clicking here to email help@lbl.gov

While this issue should not cause any loss of data, IT User Support reminds all users that all computers should be backed up, and recommends Druva inSync for this purpose.

Solution

Scenario: Windows 10 devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and have NOT YET BEEN REBOOTED

 Fix: Reference “Scenario 2” solution on Microsoft’s Support site, https://support.microsoft.com/en-us/help/4049094/windows-devices-may-fail-to-boot-after-installing-october-10-version-

 

Scenario: Windows 10 devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and are unable to boot into Windows.

 Fix: Reference “Scenario 3” solution on Microsoft’s Support site, https://support.microsoft.com/en-us/help/4049094/windows-devices-may-fail-to-boot-after-installing-october-10-version-o.

 

This project was possible because IT identified affected systems with BigFix. To get BigFix for your computer, please visit software.lbl.gov.

Why Chrome OS?

See how the IT User Support Department is trying to stretch dollars to support science, see our story at Chrome OS.

CCleaner Hacked

Problem

Some CCleaner installers were found to have third party malware embedded. Though CCleaner fixed their installers quickly, some of users downloaded and unknowingly installed malware. A project in IT User Support was initiated to identify these systems and notify users that their computers could be compromised. We requested removal of the software and a complete Sophos scan to be run to confirm removal of the infected software. We are continuing to monitor systems for potential threat using BigFix.

Solution

IT User Support advised staff to do the following:

  1. Uninstall CCleaner
  2. Run a Sophos scan. If you don’t have Sophos installed, please download for our software download page (https://software.lbl.gov)

Related news

Please note as a part of this investigation, we discovered that the free version of CCleaner cannot legally be installed on Laboratory computers. The IT User Support will be issuing a BigFix offer to remove this software at user convenience. If you don't have BigFix installed on your system please see our IT Software Download Page at https://software.lbl.gov/.

This project was possible because IT identified affected systems with BigFix. To get BigFix for your computer, please visit software.lbl.gov.

As of October 16, 2017, Adobe will no longer be supporting and providing security patches for Acrobat 11 and all previous versions. If a security vulnerability is identified after October 16, 2017, Cybersecurity may block you from our network unless you do one of two things:

Option 1: Upgrade to Adobe Acrobat DC  
Adobe has now moved to a cloud based subscription model of Adobe Acrobat, called Adobe Acrobat DC. The current cost for Adobe Acrobat DC from the Lab’s software site is $160.00 per year. This is an annual subscription with the potential to increase between 3 to 5 % annually.

There is no direct upgrade path from older versions of Adobe Acrobat to Adobe Acrobat DC.  Adobe Acrobat DC can be obtained from our Lab’s software download site, https://software.lbl.gov/swSoftwareDetails.php?applicationID=1.  As a reminder, all Adobe products should be purchased through the Lab’s software download site.

Option 2: Use an alternative PDF reader/document signing tool
CutePDF is available for free on software.lbl.gov to support PDF generation. For users who use Adobe Acrobat as a signature tool, HelloSign is a free alternative solution to Lab employees. Windows 10 and Mac users can generate PDFs using the built-in print to PDF function. If you wish to obtain further information regarding PDF generation or HelloSign, please submit your questions to help@lbl.gov.

Acrobat EOL Inquiry

 

 

Problem

There is a known Windows 7 log file compression bug. As a result of this bug log files replicate and grow filling up your hard drive effecting system performance and slowdown. Microsoft has known about the bug, but has not provided an official patch. Several users at the Lab recently have been a victim of this bug and their systems are currently being addressed. If you feel your system may be affected and your hard drive is filling up, the fix provided below should address the issue.

Solution

Follow the steps:

Before you ever make any major changes to your system, always ensure you have a full and complete back up. This will enable you to restore your system if any of the fix does not work.

  1. Stop the Windows Modules Installer service, by clicking Start and in the Search box type services.msc
  2. Scroll down to the Windows Modules Installer service and double-click on it
  3. Under Service status, click Stop, then click OK
  4. Use File Explorer to go to C:\Windows\Logs\CBS. (If Windows is installed on a different hard drive, you have to go to that drive.)\
  5. Delete all of the files in that folder
  6. For good measure, delete all the "cab*" files in your Windows Temp folder, typically C:\Windows\Temp
  7. Reboot

If you would like help with this process, please click the link below to request support.

 Request Help

 

This project was possible because IT identified affected systems with BigFix. To get BigFix for your computer, please visit software.lbl.gov.

  • No labels