Win11 24H2 KB5048667 repeatedly downloads and installs

Ads

January 2024, 12 January 2026, 1

In my environment, I am experiencing a problem where the Windows 11 version 24H2 update KB5048667 is repeatedly downloaded and installed.

KB5048667 was installed on 2024/‎12/‎11 and there had been no problems until now, but this problem suddenly occurred today.

The download of KB5048667 may stop midway and fail with an error.

Sometimes the installation will start without any errors, but the file download will not be complete and will end prematurely, causing the installation to fail.

The error code is 0x800f081f.

0x800f081f = CBS_E_SOURCE_MISSING
Component store corruption. (Package or file source not found.)

table of contents

Any thoughts on the issue of KB5048667 repeatedly downloading and installing?

The PC I use mainly is Windows 11 Home, and I previously enabledローカルグループポリシーエディターHowever, it was disabled after updating to version 24H2, so I ran a batch file to re-enable it.

While I was running this batch file, my PC started to slow down. Task managerI checked and Windows Update was running.

そして,Windows Update screenWhen I opened it, KB5048667 had started downloading.

The Local Group Policy Editor is a feature available in Windows 11 Pro and above, but is not normally available in Home.

It is unclear whether the cause of this issue is due to enabling the Local Group Policy Editor, but since the system has undergone major changes in version 24H2, it may be best to refrain from forcibly enabling something.

2024/12/22: Solution

To solve the above problem,Repairing a Windows ImageandRepair system filesI did this but it didn't improve anything.

In addition, Resetting Windows Update ComponentsBut I couldn't solve it.

The final solution was to do a system restore.

When I enabled the Local Group Policy Editor, Windows Update was performed, and a restore point was automatically created at that time.By restoring to that point, KB5048667 no longer appeared when I checked for updates on the Windows Update screen.

How to create, restore, and delete system backups

I will try to verify at a later date whether enabling the Local Group Policy Editor is the root cause.

Cause

After testing it on another PC, I found that the cause was indeed running a batch file that enabled the Local Group Policy Editor.

When I ran the batch file, the download of KB5048667 also started.

However, after testing it several times, I was able to successfully install KB5048667, so the underlying cause may lie elsewhere.

If the installation of KB5048667 is successful, KB5048667 will no longer appear when you check for updates on the Windows Update screen.

However, the Local Group Policy Editor is not a necessary feature for Windows 11 Home.

There is a possibility that the same problems as the author's PC may occur, so I do not recommend forcing it to be enabled.

2024 / 12 / 23:

The root cause was found to be the package file for enabling the Local Group Policy Editor. For details, please see the comments section of this article.

If you found this article helpful, please share it on social media.

I copied the URL!

Person who wrote this article

wenbang

Driven by questions arising from my daily PC use and the desire to "do more," I have been pursuing self-study in Windows since around 2008. I am sharing the "aha!" techniques and solutions I discovered through trial and error with the sole purpose of helping you in your PC life.

View profile

Comment:

Comment list (13)

since Than:

2024 year 12 month 23 Date 10: 33 AM

I tried a repair install again. After that, I confirmed that the Local Group Editor could no longer be started, and then I tried Windows Update, but KB5048667 has not reappeared so far. Therefore, it seems likely that enabling the Local Group Editor is triggering the problem.

I still can't run the Windows Update troubleshooting automatic diagnosis.

Reply
- wenbang Than:
  
  2024 year 12 month 23 Date 10: 38 AM
  
  Thank you, Siden.
  
  I was also unable to run the automatic diagnosis of Windows Update troubleshooting in my environment. The cause is currently unknown.
  
  Reply
- wenbang Than:
  
  2024 year 12 month 23 Date 12: 08 PM
  
  afterwards,"Fix the problem with Windows UpdateI tried running "Windows Repair", but I got the message "Windows cannot find a repair version. Please try again later" and the repair failed.
  Therefore, after uninstalling KB5048667, I ran "Fix problems with Windows Update" again, which started downloading the repair version, and proceeding with the installation resolved the problem.
  
  By the way, if you run "Fix the problem with Windows Update", the file to enable the Local Group Policy Editor will be restored.
  
  Reply
  - since Than:
    
    2024 year 12 month 23 Date 3: 14 PM
    
    It says that "Running "Fix the problem with Windows Update" will restore the files that enable the Local Group Policy Editor," but does that mean the feature itself is disabled?
    After that, the Local Group Policy Editor did not open, so does that mean it has reverted to the state before using the patch?
    
    Reply
    - wenbang Than:
      
      2024 year 12 month 23 Date 3: 34 PM
      
      Dear Siden,
      
      Yes, when you install Windows 11 version 24H2, if you have enabled features that are not available in Home, those features will be restored to their pre-enabled state.
      For example, Hyper-V is not available in Home, so it will be in the state before it was enabled.
      
      *There were no issues when I enabled Hyper-V.
      How to restore Hyper-V after updating to 24H2 on Windows 11 Home
      
      Reply
      - since Than:
        
        2024 year 12 month 23 Date 7: 04 PM
        
        I see. So the repair installation was successful and there were no problems with the sfc /scannow or DISM commands.
        Again, can we say that the problem is resolved unless the Local Group Policy Editor is re-enabled with a patch or something?
        Even after performing a repair install and running Windows Update, KB5048667 has not appeared again. Checking with PowerShell using Get-HotFix | Where-Object {$_.Description -eq “Security Update”} shows that KB5048667 is indeed installed.
        However, KB5048667 does not currently appear in the list of uninstalls in the Windows Update history. I deleted the Windows Update history, so that may be related.
        
        Also, there was one time when the screen just remained black when I started up the computer, and I wonder if that was related to the current issue. It might have been related to the graphics driver, but it's only happened once so far.
        
        Is it possible that the same problem occurred in the Pro environment and that enabling it caused the same issue in the Home environment? Well, I don't have a Pro environment so I don't know.
      - wenbang Than:
        
        2024 year 12 month 23 Date 11: 38 PM
        
        Dear Siden,
        
        Yes, I think there is no problem if you do not enable the Local Group Policy Editor. In the Pro version, it is enabled from the beginning, so there is no problem.
        
        I just checked the contents of the package file for enabling the Local Group Policy Editor and the version (build) was 10.0.26100.2454.
        10.0.26100.2454 is the version of KB5046740, the update (preview) that preceded KB5048667. This is likely the root cause of this issue.
        
        In other words, I think that because you enabled a feature from an older version than the update currently installed, Windows Update recognized it as the previous version.
        The reason there were no problems when enabling Hyper-V is probably because the version of the package file used to enable it was 10.0.26100.2605 (KB5048667).
        
        To verify this, I tried enabling the Local Group Policy Editor after running "Fix problems with Windows Update," but when I checked for updates, KB5048667 was still downloaded and installed.
        However, this time the installation was successful without any failure, and after that KB5048667 no longer appeared even when checking for updates.
since Than:

2024 year 12 month 22 Date 6: 47 PM

In my environment, I have the Local Group Policy Editor enabled on the home screen, but I haven't experienced any issues so far. Recently, after this month's regular update, I ran DISM.EXE /online /cleanup-image /restorehealth and it stalled at 62.3%. When I performed a repair install using "Fix problems with Windows Update," the Local Group Policy Editor was disabled, so I re-enabled it. However, this hasn't happened in my environment so far. I briefly wondered if that might have been the reason the DISM command stalled the first time, but I'm not sure. Incidentally, the stall at 62.3% was fixed by a repair install. However, it could have been a display issue, and running sfc /scannow instead of a repair install might have resolved the issue. If another repair install is required, I probably won't enable the Local Group Policy Editor this time.

Reply
- wenbang Than:
  
  2024 year 12 month 23 Date 2: 44 AM
  
  Thank you for your comment, Siden.
  
  I will add this to the article later, but the cause was indeed running a batch file that enables the Local Group Policy Editor.
  Did you enable the Local Group Policy Editor after installing KB5048667?
  
  Reply
  - since Than:
    
    2024 year 12 month 23 Date 7: 58 AM
    
    I don't remember the context because I didn't think it would be the cause. Is there a way to disable the Local Group Policy Editor that I enabled? It doesn't cause any problems in my current environment, though.
    
    Reply
  - since Than:
    
    2024 year 12 month 23 Date 8: 10 AM
    
    However, considering that the repair install was performed after the regular update, it must have been performed after the installation of KB5048667. After the repair install, when I checked, KB5048667 appeared again, but this time it did not prompt me to reboot. I don't know if the Local Group Policy Editor was enabled at the time. So, it seems that I am not currently in a situation where I need to repeat the installation.
    
    Reply
    - wenbang Than:
      
      2024 year 12 month 23 Date 9: 19 AM
      
      Thank you, Siden.
      
      You can remove an enabled Local Group Policy Editor by changing the command /add-package to /Remove-Package, but the files used to enable it will also be deleted, making it impossible to re-enable it. (Even if you can, an error will be displayed when you start it.)
      
      Reply
- wenbang Than:
  
  2024 year 12 month 23 Date 10: 22 AM
  
  I just deleted the Local Group Policy Editor and then ran DISM.EXE /online /cleanup-image /restorehealth, but it stopped at 62.3%.
  At this time, when I checked for updates on the Windows Update screen, the download of KB5048667 began.
  
  Then the download finishes and the installation begins, but it stops at 10% and then doesn't work at all.
  
  To verify this, I left it as it was (for over an hour), and the Windows Update service and Windows Modules Installer Worker process, which had been unresponsive for a while, started working again.
  After a while, the DISM command started working again and reached 100%, but the error: 0x800f081f (source file not found) was displayed and the Windows image repair failed.
  
  Then I closed Windows PowerShell, and after a while the installation of KB5048667 proceeded, and the installation error: 0x800f081f was displayed.
  
  Perhaps Siden had the same symptoms.
  
  Reply