The KB5048652 update has failed to install on a daily basis since it
came out. Is anybody else having this problem? If so, were you able to finally get it to install and if so, can you please tell me how you did it?
TIA.
Paul wrote:
John C. wrote:
The KB5048652 update has failed to install on a daily basis since it
came out. Is anybody else having this problem? If so, were you able to
finally get it to install and if so, can you please tell me how you did it? >>>
TIA.
Did you download it manually and apply it ?
Yes, I tried that. I downloaded this file:
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu
Attempting to install it manually resulted resulted in the following
error message: ___________________________________________________________________________________________
Download and Install Updates X
Some updates were not installed
The following updates were not installed:
Security Update for Windows (KB5048652)
[Close] ___________________________________________________________________________________________
I've spend many hours with MS's Copilot attempting to determine what the issue is and overcome it:
DISM absolutely refuses to run to completion, no matter what I do, no
matter where I tell it to find the needed files.
I really didn't want to have to elucidate what I have attempted
so far. This is why I phrased the question in my OP the way I did.
A favorite technique, is to apply the .mru by double-clicking it,
and the .mru will tell you whether the update is applicable or not.
In the past, sometimes the .mru version (an executable thing)
will work, when the Windows Update one refuses to work. The
Windows Update one is usually a bit smaller in size than the
"Cumulative" .mru version you would be downloading below.
While the listing here has 12 variants, by file size
you can see that some are the same size, and perhaps
there is no difference between the 21H2 and 22H2
versions. In any case, do your best to identify the correct one.
I made absolutely sure I was getting the correct one when I downloaded
the update .mru several days ago:
- I'm not running a 32 bit version of W10
- I'm not running an LTSB version of W10
- I'm not running an ARM64 based computer
Thus, the download I wanted was the second one from the bottom, "2024-12 Dynamic Cumulative Update for Windows 10 Version 22H2 for x64-based
Systems (KB5048652)". That download was named (and I still have that file stored away):
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu
I just attempted to redownload that file and instead got a .cab file named:
windows10.0-kb5048652-x64_59844d513d571636b5711a4a01037f5f64a98f63.cab
where the name includes the correct SHA1 value of 59844d513d571636b5711a4a01037f5f64a98f63
which I verified.
If you get the details wrong, the .mru will tell you "not for this OS",
Yes, I experienced this days ago at some point. However, when I
attempted to manually install the first download, I got no such error message.
and that is your hint to "try again". The .mru can also be blocked
if the required Servicing Stack Update (SSU) is not present. That
causes the same error code to appear.
I installed the most recent Servicing Stack Update several days ago,
when I was was attempting to manually install the update.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5048652
You can use "winver.exe" to determine your edition. Many versions
of windows have had the "winver.exe" executable onboard.
Already did this when I first noticed the problem. I'm running Windows
10 Pro version 22H2 build 19045.5131.
Articles like this map "build" to "version".
https://en.wikipedia.org/wiki/Windows_10_version_history
I am not a programmer. I'm just an end user. And my research has shown
me that I am by far not the only person experiencing the problem. It's infuriating to have to go through this kind of difficulty and see that Microsoft apparently has no intention of dealing with the issue.
Seems coincidental that this kind of thing would occur just when
Microsoft is attempting to get every Windows 10 user to go to Windows 11.
Regardless, since the download seems to have changed I'll give it
another try.
The instructions I found for using a .cab file to do the update are:
Command Prompt:
1. Open Command Prompt as an administrator.
2. Type dism /online /add-package /packagepath:"PATH\TO\CAB" and press
Enter.
3. Allow the process to finish without interruption.
The command prompt I prefer is Powershell in Administrator mode.
Thanks for replying, Paul. I appreciate your trying to help. Maybe
attempting to install the most recent download manually will work, maybe
not. I'll try it and let you know if it works.
John C. wrote:
The KB5048652 update has failed to install on a daily basis since it
came out. Is anybody else having this problem? If so, were you able to
finally get it to install and if so, can you please tell me how you did it? >>
TIA.
Did you download it manually and apply it ?
A favorite technique, is to apply the .mru by double-clicking it,
and the .mru will tell you whether the update is applicable or not.
In the past, sometimes the .mru version (an executable thing)
will work, when the Windows Update one refuses to work. The
Windows Update one is usually a bit smaller in size than the
"Cumulative" .mru version you would be downloading below.
While the listing here has 12 variants, by file size
you can see that some are the same size, and perhaps
there is no difference between the 21H2 and 22H2
versions. In any case, do your best to identify the correct one.
If you get the details wrong, the .mru will tell you "not for this OS",
and that is your hint to "try again". The .mru can also be blocked
if the required Servicing Stack Update (SSU) is not present. That
causes the same error code to appear.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5048652
You can use "winver.exe" to determine your edition. Many versions
of windows have had the "winver.exe" executable onboard.
Articles like this map "build" to "version".
https://en.wikipedia.org/wiki/Windows_10_version_history
John C. wrote:
Paul wrote:
John C. wrote:
The KB5048652 update has failed to install on a daily basis since it
came out. Is anybody else having this problem? If so, were you able to >>>> finally get it to install and if so, can you please tell me how you did it?
TIA.
Did you download it manually and apply it ?
Yes, I tried that. I downloaded this file:
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu
Attempting to install it manually resulted resulted in the following
error message:
___________________________________________________________________________________________
Download and Install Updates X
Some updates were not installed
The following updates were not installed:
Security Update for Windows (KB5048652)
[Close]
___________________________________________________________________________________________
I've spend many hours with MS's Copilot attempting to determine what the
issue is and overcome it:
DISM absolutely refuses to run to completion, no matter what I do, no
matter where I tell it to find the needed files.
I really didn't want to have to elucidate what I have attempted
so far. This is why I phrased the question in my OP the way I did.
A favorite technique, is to apply the .mru by double-clicking it,
and the .mru will tell you whether the update is applicable or not.
In the past, sometimes the .mru version (an executable thing)
will work, when the Windows Update one refuses to work. The
Windows Update one is usually a bit smaller in size than the
"Cumulative" .mru version you would be downloading below.
While the listing here has 12 variants, by file size
you can see that some are the same size, and perhaps
there is no difference between the 21H2 and 22H2
versions. In any case, do your best to identify the correct one.
I made absolutely sure I was getting the correct one when I downloaded
the update .mru several days ago:
- I'm not running a 32 bit version of W10
- I'm not running an LTSB version of W10
- I'm not running an ARM64 based computer
Thus, the download I wanted was the second one from the bottom, "2024-12
Dynamic Cumulative Update for Windows 10 Version 22H2 for x64-based
Systems (KB5048652)". That download was named (and I still have that file
stored away):
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu
I just attempted to redownload that file and instead got a .cab file named: >>
windows10.0-kb5048652-x64_59844d513d571636b5711a4a01037f5f64a98f63.cab
where the name includes the correct SHA1 value of
59844d513d571636b5711a4a01037f5f64a98f63
which I verified.
If you get the details wrong, the .mru will tell you "not for this OS",
Yes, I experienced this days ago at some point. However, when I
attempted to manually install the first download, I got no such error
message.
and that is your hint to "try again". The .mru can also be blocked
if the required Servicing Stack Update (SSU) is not present. That
causes the same error code to appear.
I installed the most recent Servicing Stack Update several days ago,
when I was was attempting to manually install the update.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5048652
You can use "winver.exe" to determine your edition. Many versions
of windows have had the "winver.exe" executable onboard.
Already did this when I first noticed the problem. I'm running Windows
10 Pro version 22H2 build 19045.5131.
Articles like this map "build" to "version".
https://en.wikipedia.org/wiki/Windows_10_version_history
I am not a programmer. I'm just an end user. And my research has shown
me that I am by far not the only person experiencing the problem. It's
infuriating to have to go through this kind of difficulty and see that
Microsoft apparently has no intention of dealing with the issue.
Seems coincidental that this kind of thing would occur just when
Microsoft is attempting to get every Windows 10 user to go to Windows 11.
Regardless, since the download seems to have changed I'll give it
another try.
The instructions I found for using a .cab file to do the update are:
Command Prompt:
1. Open Command Prompt as an administrator.
2. Type dism /online /add-package /packagepath:"PATH\TO\CAB" and press
Enter.
3. Allow the process to finish without interruption.
The command prompt I prefer is Powershell in Administrator mode.
Thanks for replying, Paul. I appreciate your trying to help. Maybe
attempting to install the most recent download manually will work, maybe
not. I'll try it and let you know if it works.
As I expected, it didn't work: ______________________________________________________________________________________
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.5131
Processing 1 of 1 - Adding package Multiple_Packages~~~~0.0.0.0
[= 3.0% ]
An error occurred - Error: 0x800f0831
Error: 0x800f0831
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32> ______________________________________________________________________________________
On Sat, 1/11/2025 10:13 AM, John C. wrote:
John C. wrote:
Paul wrote:
John C. wrote:
The KB5048652 update has failed to install on a daily basis since it >>>>> came out. Is anybody else having this problem? If so, were you able to >>>>> finally get it to install and if so, can you please tell me how you did it?
TIA.
Did you download it manually and apply it ?
Yes, I tried that. I downloaded this file:
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu
Attempting to install it manually resulted resulted in the following
error message:
___________________________________________________________________________________________
Download and Install Updates X
Some updates were not installed
The following updates were not installed:
Security Update for Windows (KB5048652)
[Close]
___________________________________________________________________________________________
I've spend many hours with MS's Copilot attempting to determine what the >>> issue is and overcome it:
DISM absolutely refuses to run to completion, no matter what I do, no
matter where I tell it to find the needed files.
I really didn't want to have to elucidate what I have attempted
so far. This is why I phrased the question in my OP the way I did.
A favorite technique, is to apply the .mru by double-clicking it,
and the .mru will tell you whether the update is applicable or not.
In the past, sometimes the .mru version (an executable thing)
will work, when the Windows Update one refuses to work. The
Windows Update one is usually a bit smaller in size than the
"Cumulative" .mru version you would be downloading below.
While the listing here has 12 variants, by file size
you can see that some are the same size, and perhaps
there is no difference between the 21H2 and 22H2
versions. In any case, do your best to identify the correct one.
I made absolutely sure I was getting the correct one when I downloaded
the update .mru several days ago:
- I'm not running a 32 bit version of W10
- I'm not running an LTSB version of W10
- I'm not running an ARM64 based computer
Thus, the download I wanted was the second one from the bottom, "2024-12 >>> Dynamic Cumulative Update for Windows 10 Version 22H2 for x64-based
Systems (KB5048652)". That download was named (and I still have that file >>> stored away):
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu
I just attempted to redownload that file and instead got a .cab file named: >>>
windows10.0-kb5048652-x64_59844d513d571636b5711a4a01037f5f64a98f63.cab
where the name includes the correct SHA1 value of
59844d513d571636b5711a4a01037f5f64a98f63
which I verified.
If you get the details wrong, the .mru will tell you "not for this OS", >>>Yes, I experienced this days ago at some point. However, when I
attempted to manually install the first download, I got no such error
message.
and that is your hint to "try again". The .mru can also be blocked
if the required Servicing Stack Update (SSU) is not present. That
causes the same error code to appear.
I installed the most recent Servicing Stack Update several days ago,
when I was was attempting to manually install the update.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5048652
You can use "winver.exe" to determine your edition. Many versions
of windows have had the "winver.exe" executable onboard.
Already did this when I first noticed the problem. I'm running Windows
10 Pro version 22H2 build 19045.5131.
Articles like this map "build" to "version".
https://en.wikipedia.org/wiki/Windows_10_version_history
I am not a programmer. I'm just an end user. And my research has shown
me that I am by far not the only person experiencing the problem. It's
infuriating to have to go through this kind of difficulty and see that
Microsoft apparently has no intention of dealing with the issue.
Seems coincidental that this kind of thing would occur just when
Microsoft is attempting to get every Windows 10 user to go to Windows 11. >>>
Regardless, since the download seems to have changed I'll give it
another try.
The instructions I found for using a .cab file to do the update are:
Command Prompt:
1. Open Command Prompt as an administrator.
2. Type dism /online /add-package /packagepath:"PATH\TO\CAB" and press
Enter.
3. Allow the process to finish without interruption.
The command prompt I prefer is Powershell in Administrator mode.
Thanks for replying, Paul. I appreciate your trying to help. Maybe
attempting to install the most recent download manually will work, maybe >>> not. I'll try it and let you know if it works.
As I expected, it didn't work:
______________________________________________________________________________________
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.5131
Processing 1 of 1 - Adding package Multiple_Packages~~~~0.0.0.0
[= 3.0% ]
An error occurred - Error: 0x800f0831
Error: 0x800f0831
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32>
______________________________________________________________________________________
I haven't seen this one explained in terms I can understand.
Something is missing. Whatever is missing, seems hard to fix.
0x800F0831
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update
"<Missing_Package> represents the package for which the manifest is missing"
Component Based Servicing (CBS) is driven by manifest files.
WinSxS is full of manifest files.
LCU contains the Last Cumulative Update.
This is great.
Yet, these softwares are complaining that a particular
manifest is missing.
As I understand it, not even a Repair Install fixes this.
If I see something regarding exactly what is wrong,
I will report back. But at the moment, I don't
know what is wrong, and why simpler repair methods
can't/won't work. It's possible that WinSxS gets "scanned"
before the repair procedure starts, and something becomes
wobbly enough to stop the repair attempt.
Really, this is what Repair Installs should fix, because
the Windows becomes Windows.old, and a new WinSxS is built
from scratch.
For a repair install, you mount the .iso file for the
Windows installer ISO which is the same version as
what you're running. And while the OS is booted,
you run Setup.exe off the mounted ISO. That's a Repair install.
I've used that a couple times, as a lazy way to get a result.
But it might not work for this one. Why ? Damned if I know why.
I downloaded the latest version of the Media Creation Tool (MediaCreationTool_22H2.exe) which should be more up to date than what I
used to install W10 Pro a few months ago. i used it to make an install
thumb drive. The last chance I have to make this work is to reinstall
W10 Pro from it, using the option to "Keep personal files and apps".
This is a deplorable thing to have to do, but it would appear that I
have no choice. If this doesn't work, then I will have to do a complete reinstall. I will be seriously pissed off if this happens.
Yes, I will back up all my data. I always do that. And yes, I do have
every setup filed needed to reinstall all drivers and programs that I'm currently using.
I downloaded the latest version of the Media Creation Tool (MediaCreationTool_22H2.exe) which should be more up to date than
what I used to install W10 Pro a few months ago. i used it to make an
install thumb drive. The last chance I have to make this work is to
reinstall W10 Pro from it, using the option to "Keep personal files
and apps".
This is a deplorable thing to have to do, but it would appear that I
have no choice. If this doesn't work, then I will have to do a
complete reinstall. I will be seriously pissed off if this happens.
Yes, I will back up all my data. I always do that. And yes, I do have
every setup filed needed to reinstall all drivers and programs that
I'm currently using.
I downloaded the latest version of the Media Creation Tool >(MediaCreationTool_22H2.exe) which should be more up to date than what I
used to install W10 Pro a few months ago. i used it to make an install
thumb drive. The last chance I have to make this work is to reinstall
W10 Pro from it, using the option to "Keep personal files and apps".
Paul wrote:
On Sat, 1/11/2025 10:13 AM, John C. wrote:
John C. wrote:
Paul wrote:
John C. wrote:
The KB5048652 update has failed to install on a daily basis since it >>>>>> came out. Is anybody else having this problem? If so, were you able to >>>>>> finally get it to install and if so, can you please tell me how you did it?
TIA.
Did you download it manually and apply it ?
Yes, I tried that. I downloaded this file:
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu >>>>
Attempting to install it manually resulted resulted in the following
error message:
___________________________________________________________________________________________
Download and Install Updates X
Some updates were not installed
The following updates were not installed:
Security Update for Windows (KB5048652)
[Close]
___________________________________________________________________________________________
I've spend many hours with MS's Copilot attempting to determine what the >>>> issue is and overcome it:
DISM absolutely refuses to run to completion, no matter what I do, no
matter where I tell it to find the needed files.
I really didn't want to have to elucidate what I have attempted
so far. This is why I phrased the question in my OP the way I did.
A favorite technique, is to apply the .mru by double-clicking it,
and the .mru will tell you whether the update is applicable or not.
In the past, sometimes the .mru version (an executable thing)
will work, when the Windows Update one refuses to work. The
Windows Update one is usually a bit smaller in size than the
"Cumulative" .mru version you would be downloading below.
While the listing here has 12 variants, by file size
you can see that some are the same size, and perhaps
there is no difference between the 21H2 and 22H2
versions. In any case, do your best to identify the correct one.
I made absolutely sure I was getting the correct one when I downloaded >>>> the update .mru several days ago:
- I'm not running a 32 bit version of W10
- I'm not running an LTSB version of W10
- I'm not running an ARM64 based computer
Thus, the download I wanted was the second one from the bottom, "2024-12 >>>> Dynamic Cumulative Update for Windows 10 Version 22H2 for x64-based
Systems (KB5048652)". That download was named (and I still have that file >>>> stored away):
windows10.0-kb5048652-x64_279b3aca56a2aa72aa2d08ccc30fad69bd5a1e29.msu >>>>
I just attempted to redownload that file and instead got a .cab file named:
windows10.0-kb5048652-x64_59844d513d571636b5711a4a01037f5f64a98f63.cab >>>>
where the name includes the correct SHA1 value of
59844d513d571636b5711a4a01037f5f64a98f63
which I verified.
If you get the details wrong, the .mru will tell you "not for this OS", >>>>Yes, I experienced this days ago at some point. However, when I
attempted to manually install the first download, I got no such error
message.
and that is your hint to "try again". The .mru can also be blocked
if the required Servicing Stack Update (SSU) is not present. That
causes the same error code to appear.
I installed the most recent Servicing Stack Update several days ago,
when I was was attempting to manually install the update.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5048652
You can use "winver.exe" to determine your edition. Many versions
of windows have had the "winver.exe" executable onboard.
Already did this when I first noticed the problem. I'm running Windows >>>> 10 Pro version 22H2 build 19045.5131.
Articles like this map "build" to "version".
https://en.wikipedia.org/wiki/Windows_10_version_history
I am not a programmer. I'm just an end user. And my research has shown >>>> me that I am by far not the only person experiencing the problem. It's >>>> infuriating to have to go through this kind of difficulty and see that >>>> Microsoft apparently has no intention of dealing with the issue.
Seems coincidental that this kind of thing would occur just when
Microsoft is attempting to get every Windows 10 user to go to Windows 11. >>>>
Regardless, since the download seems to have changed I'll give it
another try.
The instructions I found for using a .cab file to do the update are:
Command Prompt:
1. Open Command Prompt as an administrator.
2. Type dism /online /add-package /packagepath:"PATH\TO\CAB" and press >>>> Enter.
3. Allow the process to finish without interruption.
The command prompt I prefer is Powershell in Administrator mode.
Thanks for replying, Paul. I appreciate your trying to help. Maybe
attempting to install the most recent download manually will work, maybe >>>> not. I'll try it and let you know if it works.
As I expected, it didn't work:
______________________________________________________________________________________
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.5131
Processing 1 of 1 - Adding package Multiple_Packages~~~~0.0.0.0
[= 3.0% ]
An error occurred - Error: 0x800f0831
Error: 0x800f0831
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32>
______________________________________________________________________________________
I haven't seen this one explained in terms I can understand.
Something is missing. Whatever is missing, seems hard to fix.
0x800F0831
https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update
"<Missing_Package> represents the package for which the manifest is missing"
Component Based Servicing (CBS) is driven by manifest files.
WinSxS is full of manifest files.
LCU contains the Last Cumulative Update.
This is great.
Yet, these softwares are complaining that a particular
manifest is missing.
As I understand it, not even a Repair Install fixes this.
If I see something regarding exactly what is wrong,
I will report back. But at the moment, I don't
know what is wrong, and why simpler repair methods
can't/won't work. It's possible that WinSxS gets "scanned"
before the repair procedure starts, and something becomes
wobbly enough to stop the repair attempt.
Really, this is what Repair Installs should fix, because
the Windows becomes Windows.old, and a new WinSxS is built
from scratch.
For a repair install, you mount the .iso file for the
Windows installer ISO which is the same version as
what you're running. And while the OS is booted,
you run Setup.exe off the mounted ISO. That's a Repair install.
I've used that a couple times, as a lazy way to get a result.
But it might not work for this one. Why ? Damned if I know why.
I downloaded the latest version of the Media Creation Tool (MediaCreationTool_22H2.exe) which should be more up to date than what I
used to install W10 Pro a few months ago. i used it to make an install
thumb drive. The last chance I have to make this work is to reinstall
W10 Pro from it, using the option to "Keep personal files and apps".
This is a deplorable thing to have to do, but it would appear that I
have no choice. If this doesn't work, then I will have to do a complete reinstall. I will be seriously pissed off if this happens.
Yes, I will back up all my data. I always do that. And yes, I do have
every setup filed needed to reinstall all drivers and programs that I'm currently using.
John C. wrote:
I downloaded the latest version of the Media Creation Tool
(MediaCreationTool_22H2.exe) which should be more up to date than what I
used to install W10 Pro a few months ago. i used it to make an install
thumb drive. The last chance I have to make this work is to reinstall
W10 Pro from it, using the option to "Keep personal files and apps".
That's what I did, after trying several other "fixes", and failing. The repair install did the trick.
John C. wrote:
I downloaded the latest version of the Media Creation Tool
(MediaCreationTool_22H2.exe) which should be more up to date than
what I used to install W10 Pro a few months ago. i used it to make an
install thumb drive. The last chance I have to make this work is to
reinstall W10 Pro from it, using the option to "Keep personal files
and apps".
This is a deplorable thing to have to do, but it would appear that I
have no choice. If this doesn't work, then I will have to do a
complete reinstall. I will be seriously pissed off if this happens.
Yes, I will back up all my data. I always do that. And yes, I do have
every setup filed needed to reinstall all drivers and programs that
I'm currently using.
If you have icons on your monitor screen I would make and save an image file of the monitor screen. I had this problem and had to do a repair install.
I am still working on getting everything reinstalled. I stopped to see if the computer will have a problem installing the next cumulative update
before I go any further. It is a nightmare when this happens.
Just opened Powershell as an administrator and ran the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<Computer name>\c$\winsxs /LimitAccess
where "<Computer name>" is the name of my computer. The results were: ______________________________________________________________________________
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.5131
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a
source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32> ______________________________________________________________________________
All that file tells me is
How can DISM run to 100% and yet still give me a stupid error message
like that?? Could this problem perhaps be related to my
C:\Windows\WinSxS folder being 11.7gb in size???
Windows 10 is a complete abortion in my NSHO. A huge, unstable house of cards.
On Mon, 1/13/2025 9:11 AM, John C. wrote:
Just opened Powershell as an administrator and ran the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<Computer
name>\c$\winsxs /LimitAccess
where "<Computer name>" is the name of my computer. The results were:
______________________________________________________________________________
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.5131
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are
required to restore the feature. For more information on specifying a
source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32>
______________________________________________________________________________
All that file tells me is
How can DISM run to 100% and yet still give me a stupid error message
like that?? Could this problem perhaps be related to my
C:\Windows\WinSxS folder being 11.7gb in size???
Windows 10 is a complete abortion in my NSHO. A huge, unstable house of
cards.
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:K:\Windows /LimitAccess
On Mon, 1/13/2025 9:11 AM, John C. wrote:
Just opened Powershell as an administrator and ran the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<Computer
name>\c$\winsxs /LimitAccess
where "<Computer name>" is the name of my computer. The results were:
______________________________________________________________________________
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.5131
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are
required to restore the feature. For more information on specifying a
source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\Windows\system32>
______________________________________________________________________________
All that file tells me is
How can DISM run to 100% and yet still give me a stupid error message
like that?? Could this problem perhaps be related to my
C:\Windows\WinSxS folder being 11.7gb in size???
Windows 10 is a complete abortion in my NSHO. A huge, unstable house of
cards.
[Picture]
https://i.postimg.cc/ZRk9drkM/Windows-Side-by-Side-sizes.gif
You can run Process Monitor and collect a trace during a DISM run,
and see where it has been scanning.
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
If we look at your command:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\MySecondComputer\c$\winsxs /LimitAccess
the LimitAccess says to not use Windows Update for repair material, and to use MySecondComputer
as an authoritative source of a WinSxS.
Whereas the command reference web page gives as an example:
/Source:c:\test\mount\windows
and then our command might look like this (slight change). The repair source is
just above the WinSxS folder.
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\MySecondComputer\c$\Windows /LimitAccess
The C$ implies an Administrative share, which I presume is accessible for some reason.
It should exist, but I don't know how smoothly that works.
I took a backup of MySecondComputer using Macrium, put it on the broken machine,
and Macrium on that machine, can mount the backed up C: as drive letter K: . Both machines have the same Winver.
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:K:\Windows /LimitAccess
And here it is, part way through, in-flight.
[Picture]
https://i.postimg.cc/wjm9nMbX/test-run-DISM-disk33.gif
It's all over, Paul. I won the battle. Kind of. I did a repair
reinstall and then KB5048652 finally installed. And now the work of straightening up the absolute mess begins.
At this point I am in an absolutely black rage. Fuck Microsoft. Fuck
Windows.
Thanks for trying to help though.
John C. wrote:
It's all over, Paul. I won the battle. Kind of. I did a repair
reinstall and then KB5048652 finally installed. And now the work of
straightening up the absolute mess begins.
At this point I am in an absolutely black rage. Fuck Microsoft. Fuck
Windows.
Thanks for trying to help though.
At least my repair install computer updated with the cumulative update today without a problem. Now back to finishing cleaning up the mess.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 508 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 214:49:16 |
| Calls: | 9,972 |
| Calls today: | 3 |
| Files: | 13,831 |
| Messages: | 6,358,274 |
