Windows 10 1511 & SCCM CB WSUS Error – 0x80240fff

I recently encountered an error on all Windows 10 version 1511 scanning against the SCCM CB lab environment for updates.

 

The error messages in WUAhandler.log on a Windows 10 version 1511

“OnSearchComplete – Failed to end search job. Error = 0x80240fff”

“Scan failed with error = 0x80240fff”

The Windowsupdate.log provides more information,  for 1511 you’ll need to run the PowerShell command Get-WindowsUpdatelog to generate a readable log file to get more valuable information

 

 

Opening the log it shows some error messages:

Two Swap OSUpgrades are found, Update1 = {7F016D4C-C9A6-4699-A7DA-3D86EF81843F}.201, Update2 = {83695761-2AAC-4890-B68E-94B01BAC720C}
FilterInappropriateOSUpgrade failed, hr=80240FFF
Exit code = 0x80240FFF

Now I need to identify the update ID’s shown in the error log and translate into English

Fire up SQL Management Studio on you top level site and run the following SQL query populating the update ID’s

 

Make sure you change the DB name to your environment

FROM [CM_LAB].[dbo].[v_UpdateInfo]

and replace the CI_UniqueID = ‘7F016D4C-C9A6-4699-A7DA-3D86EF81843F‘  value

SELECT [CI_ID]
      ,[CI_UniqueID]
      ,[ModelId]
      ,[ModelName]
      ,[SDMPackageVersion]
      ,[SDMPackageDigest]
      ,[CIType_ID]
      ,[CIVersion]
      ,[DateCreated]
      ,[DateLastModified]
      ,[LastModifiedBy]
      ,[CreatedBy]
      ,[PermittedUses]
      ,[IsBundle]
      ,[IsHidden]
      ,[IsTombstoned]
      ,[IsUserDefined]
      ,[IsEnabled]
      ,[IsExpired]
      ,[SourceSite]
      ,[ContentSourcePath]
      ,[ApplicabilityCondition]
      ,[CI_CRC]
      ,[Precedence]
      ,[ConfigurationFlags]
      ,[EULAExists]
      ,[EULAAccepted]
      ,[EULASignoffDate]
      ,[EULASignoffUser]
      ,[IsQuarantined]
      ,[EffectiveDate]
      ,[ModifiedTime]
      ,[IsDeployed]
      ,[IsSuperseded]
      ,[IsChild]
      ,[InUse]
      ,[IsLatest]
      ,[IsBroken]
      ,[PlatformType]
      ,[IsUserCI]
      ,[RevisionTag]
      ,[IsSignificantRevision]
      ,[SedoObjectVersion]
      ,[ApplicableAtUserLogon]
      ,[BulletinID]
      ,[ArticleID]
      ,[Severity]
      ,[CustomSeverity]
      ,[DatePosted]
      ,[DateRevised]
      ,[RevisionNumber]
      ,[MaxExecutionTime]
      ,[RequiresExclusiveHandling]
      ,[UpdateSource_ID]
      ,[MinSourceVersion]
      ,[LocaleID]
      ,[Title]
      ,[Description]
      ,[InfoURL]
      ,[UpdateType]
      ,[Locales]
  FROM [CM_LAB].[dbo].[v_UpdateInfo]
  WHERE CI_UniqueID = '7F016D4C-C9A6-4699-A7DA-3D86EF81843F' 
  OR CI_UniqueID = '83695761-2AAC-4890-B68E-94B01BAC720C'

 

The results are shown below, look for the title…

Now I know two updates could be the problem, considering 1607 has been available for a while and the problem only started with 1703 lets focus on that particular update

Feature update to Windows 10 Enterprise, version 1703, en-us

The following are changes made in a Lab environment, for Production Systems it is best to log a MS Support ticket.

 

Fire up the WSUS console and select the filter shown below

 

Search for the update title returned in the SQL query and choose decline

Once declined the problem machine should complete a WSUS scan

If you’re worried about declining updates from the WSUS console, you can always set them back to not approved. Once a full sync occurs with SCCM SUP (Top Level) the updates will show green again for deployment.

 

For returning the updates declined back to normal, locate the declined updates in the WSUS console

 

Right click the update and select approve

Then select not approved

And OK

 

This will reverse the changes made, next thing is to have the update show green in SCCM. This is the tricky part, because a full sync of WSUS is required from the top level site. Just setting a custom schedule wont achieve a full sync, you will need to change a setting for this to work.

Navigate to Administration > Site Configuration > Sites and select your top level site (the site that syncs with Microsoft) in my case its the Primary

Choose Configure Site Components > Software Update Point

I changed the setting Do not expire updates and bumped up the time limit to 4 months, I need to do this for a full sync to occur ( You can change this back once the full sync completes).

 

Now select the sync schedule tab and choose Custom schedule

Set this 5 minutes into the future

Click ok and open the wsyncmgr.log on the top level site server, you should start to see the updates resync back into the DB. This may take a few hours.

SCCM Console – Before

After

 

 

Best advice:

Log a support case with MS.

 

 

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Get in touch

Your Name (required)

Your Email (required)

Subject

Your Message

Book a Demo

Your Name (required)

Your Email (required)

Phone Number(Optional)