July patches were re-released 7/13

I need a solution

I haven’t been able to find out what changed, but Microsoft’s July patches originally released 7/10 were re-released on 7/13.

This Microsoft site shows the new modify dates

https://www.catalog.update.microsoft.com/Search.aspx?q=2018-07

I have a ticket in with support to see if Tuesday’s PMImport will include the new revisions.  I will report back.  I don’t think WSUS customers are seeing the new bulletins yet.

0

Related:

Latest Win10 update corrupts SEP14

I need a solution

The latest Microsoft patch for Windows 10 Fall Creators Update (1709, aka Build 16299) is causing Symantec Endpoint Protection 14.0 RU1 MP1 (14.0.3876.1100) to report “Product Error requires attention” and the SEP system tray icon to report “There are multiple problems (2)”. I thought you might want to work with Microsoft or create another SEP patch to fix this issue.

The patch I applied today, which you can get from the Microsoft Update Catalog and also through our corporate WSUS server downloads is KB4056892. After applying the patch, the Win10 version reports Build 16299.192.

When I remove the above Microsoft patch, SEP 14 no longer reports errors.

Please fix when you can.

0

Related:

Windows 10 compatibility support?

I need a solution

Currently, Symantec Encryption Desktop does not seem to support Windows 10 feature updates.  With feature updates being released twice a year, and only supported for 18 months from the release of the feature update, this presents an issue for clients that are not reimaged every 18 monthes.

It seems we can update Windows 10 by decrypting the computer first, but this seems an untenable solution for many hundreds of clients.  I found an article referring to a feature request to push the Anniversary update form WSUS, but it says “Support has worked directly with Product Management and has determined this feature will not be included at this time.”  https://support.symantec.com/en_US/article.INFO4002.html  I have also found an article referring to some scripts for creating installation media for upgrades, but many of our users are remote workers.

Does this mean Symantec has no plans at this time to make the ability to upgrade Windows 10 without decryption possible?  

Or can someone provide information I may have missed explaining the procedure to update Windows 10 clients without decrypting first?

Thank you.

Doug

0

Related:

WSUS console reports 100% installed but there are still needed updates

Has anyone ever seen this issue? My WSUS server was working correctly until I started testing WSUS Package Publisher as a way to push apps and updates to Windows machines since we do not allow our users to have local admin rights.

The WSUS console shows 100% in the Installed/Not Applicable section but in the update view for the client machines I am still seeing some needed updates.

Related:

The catalog was last synchronized successfully %1 or more days ago.

Details
Product: .NET Framework
Event ID: 10021
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: HealthCoreCatalogSyncYellow
Message: The catalog was last synchronized successfully %1 or more days ago.
   
Explanation
WSUS catalog synchronization depends on connectivity to the upstream server or Microsoft Update.
   
User Action
Old Catalog Synchronization

The last catalog synchronization happened some time ago or was never performed.

  1. This is a reminder to synchronize the server on a regular
    basis if the synchronization schedule is set to manual.
  2. Start WSUS 3.0: Click Start, click Administrative Tools, then click Microsoft Windows Server Update Services v3.0.
  3. Click Synchronization Results.
  4. In the Action pane, click Synchronize Now.

Verify

Look for the corresponding error event.

  1. Open a command window.
  2. Type cd <WSUSInstallDir>\Tools
  3. Type wsusutil checkhealth
  4. Type eventvwr
  5. Review the Application log for the most recent events from
    source Windows Server Update Services and event id 10020.

Related:

The Windows Server Update Server Service has stopped.

Details
Product: .NET Framework
Event ID: 502
Source: Windows Server Update Services
Version: 2.0.50727
Symbolic Name: WsusServiceStopped
Message: The Windows Server Update Server Service has stopped.
   
Explanation
The WSUS service must be running.
   
User Action
WSUS Service

The WSUS service “Update Services” is stopped.

Possible resolutions include:

  • The Update Services service has been manually stopped. Start the service.
  1. Open a command window.
  2. Type sc start wsusservice
  • The Update Services service is set to manual and is stopped.
    1. Open a command window.
    2. Type sc config wsusservice start= auto
    3. Type sc start wsusservice
  • The Update Services service failed to start. Review the NT event log for issues that occurred before this event (for example, the SQL database or IIS) and resolve them. Then start the service.
    1. Open a command window.
    2. Type sc start wsusservice

    Verify

    Look for the corresponding error event.

    1. Open a command window.
    2. Type cd <WSUSInstallDir>\Tools
    3. Type wsusutil checkhealth
    4. Type eventvwr
    5. Review the Application log for the most recent events from
      source Windows Server Update Services and event id 501.

    Related: