• Update KB5048652 won't install

    From John C.@21:1/5 to All on Fri Dec 20 07:10:54 2024
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to overcome
    it and if so, would you please tell me how?

    TIA

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Bradshaw@21:1/5 to John C. on Fri Dec 20 09:45:35 2024
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to
    overcome it and if so, would you please tell me how?

    TIA

    If you look down through the messages I had a problem and finally ended starting over on one of my computers. I am just curious when you look at
    the windows update history was KB5001716 installed before the failure?
    --
    <Bill>

    Brought to you from Anchorage, Alaska

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Fri Dec 20 13:18:27 2024
    "John C." <r9jmg0@yahoo.com> wrote:

    KB5048652

    https://answers.microsoft.com/en-us/windows/forum/all/kb5048652-fail-0x800f0922/661018fe-d3eb-42a4-b9f0-6026d7a8e57b?page=2

    Some users reported that multiple installs of the same update have
    occurred for them. When an update itself gets updated, it KB number
    doesn't change, but the WU client sees it as a new update. I suspect
    you'll have to wait a month, or two, for Microsoft to get their shit
    cleaned out to come up with yet another version of the same KB update to
    get it working. In prior Windows versions, you could elect to hide some updates, because you didn't want them, or they didn't apply to your
    setup (too often they were pushed whether you had the software or not,
    like patches to Skype although it wasn't installed). Hiding made it
    easier to ignore the unwanted updates. However, when an update itself
    got updated to a new version, the hide didn't work on the new version.

    https://support.microsoft.com/en-us/topic/december-10-2024-kb5048652-os-builds-19044-5247-and-19045-5247-454fbd4c-0723-449e-915b-8515ab41f8e3

    The KB articles have, for a long time, been uninformative. This one
    notes "This update addresses security issues for your Windows operating
    system" but give no details on what are the security issues.

    When I scroll down to the Improvements section, and click on "Windows 10
    22H2" expandable section (since I don't have the LTSC edition, and
    probably don't, either), there is mention "Important: Use EKB KB5015684
    to update to Windows 10, version 22H2" which points to:

    https://support.microsoft.com/en-us/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61

    However, you're already at 22H2. Rather than use the unfriendly update
    log in Windows, I often resort to using Belarv Advisor. Easier to read,
    and I can search, too. At the bottom of the default page is a few of
    the hotfixes that have been installed (in past 90 days). Click on the
    "See all" link to get a list.

    https://www.belarc.com/products/belarc-advisor

    Nirsoft also has their Windows Updates Viewer.

    https://www.nirsoft.net/utils/windows_updates_history_viewer.html

    Belarc can point out missing updates. Nirsoft can point out failed or
    aborted ones.

    https://www.youtube.com/watch?v=5d5Ug0DUeo8
    44 patched vulnerabilities.
    36 are important.
    8 are critical: remote code execution vulnerabilities.
    Where did he get that info?

    Microsoft Update Catalog for KB5048652 https://www.catalog.update.microsoft.com/Search.aspx?q=5048652

    Which one did you pick? The GDR (General Distribution Release) DU
    (Dynamic Update) ones require an Internet connect to their WSUS server.

    I remember in Windows 7 that a failed update was often fixed by deleting
    the local update cache (C:\Windows\SoftwareDistribution\Download, delete everything underneath) to force the WU to rebuild its catalog. Haven't
    had to do that in Windows 10.

    https://www.minitool.com/news/kb5048652-not-installing.html

    That mentions running a Windows Update Troubleshooter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John C. on Fri Dec 20 17:37:49 2024
    On Fri, 12/20/2024 10:10 AM, John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to overcome
    it and if so, would you please tell me how?

    TIA


    The 0x800f0831 may mean, that it was looking for the manifest
    of a previous Cumulative Update for some reason, and not finding it.
    It's possible the first install attempt, erased the last cumulative
    stored in Servicing\LCU and that is why the second error showed up
    on the second try.

    I noticed something funny going on, with my Win10 on the 5950X machine.
    I could see one of the services burning up cycles. Normally, the memory
    amount moves up and down, while it computes supersedence. Well, there
    was no disk activity, and also, the amount of memory used was not changing.

    I selected a restart, knowing that it had the choice of continuing
    the install in the shutting-down state. This did not look like it
    was going to work, and it spent at least another half hour in that state, before I started my "doing stuff to break a deadlock" to it, and it
    finally moved along.

    The suggestions at this point, are:

    skim though %WinDir%\Logs\CBS\CBS.log

    and look for any sort of sign, that it can be recovered and finish the update.

    The other suggestion is a Repair Install, from one of the Windows enthusiast sites.
    The missing manifest error, may not be recoverable from a sequential point of view, and the Repair Install is a chance to tip the Windows Update upright again. The update sequence will be different, the "previous" update
    will be different, and so on. A second chance, using fresh soup broth.

    Not even resetting Windows Update could fix this. An update SHOULD NOT
    be using the manifest of a previous update like this. The whole idea
    behind Windows Update, is prefaced on wsusscn2.cab (a giant tree of info
    about which update depends on which other update). If the turkeys at
    Microsoft have abandoned their responsibility to prepare info for
    the wsusscn2.cab file, and instead are relying upon "checking some
    old and unreliable record keeping scheme", now... how is that
    going to turn out ? Great balls of fire.

    To do a Repair Install.

    1) Run winver.exe and make sure you know which Win10 you are currently on.
    Try to match the version, with your Windows 10 install ISO file.
    the reason I did not write "use the 19045 one", is some people did not
    have the hardware to finish 19045, so the instruction for them, is to
    use the same version they are currently running (might be 19044).
    My Optiplex 780 could not install 19045, until I put a graphics card in it.
    Without the improved graphics card, it kept rolling back 19045.

    2) Right click the selected ISO, and select Mount. Alternately, if in File Explorer
    and Mount is not offered, try to Open the ISO while in File Explorer.

    3) When the virtual DVD drive opens, run the Setup.exe on the virtual DvD.

    4) An install will be done, preserving User Files and User Programs.

    5) Later, there will be C:\Windows.old and that will either disappear in
    ten days time on its own, or you can get rid of it with cleanmgr.exe .

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Bill Bradshaw on Sun Dec 22 15:04:55 2024
    Bill Bradshaw wrote:
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to
    overcome it and if so, would you please tell me how?

    TIA

    If you look down through the messages I had a problem and finally ended starting over on one of my computers. I am just curious when you look at
    the windows update history was KB5001716 installed before the failure?

    Thanks for replying, Bill.

    Yes, KB5001716 was installed 2024-‎10-‎16.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Mon Dec 23 04:37:52 2024
    VanguardLH wrote:
    "John C." <r9jmg0@yahoo.com> wrote:

    KB5048652

    https://answers.microsoft.com/en-us/windows/forum/all/kb5048652-fail-0x800f0922/661018fe-d3eb-42a4-b9f0-6026d7a8e57b?page=2

    Some users reported that multiple installs of the same update have
    occurred for them. When an update itself gets updated, it KB number
    doesn't change, but the WU client sees it as a new update. I suspect
    you'll have to wait a month, or two, for Microsoft to get their shit
    cleaned out to come up with yet another version of the same KB update to
    get it working. In prior Windows versions, you could elect to hide some updates, because you didn't want them, or they didn't apply to your
    setup (too often they were pushed whether you had the software or not,
    like patches to Skype although it wasn't installed). Hiding made it
    easier to ignore the unwanted updates. However, when an update itself
    got updated to a new version, the hide didn't work on the new version.

    https://support.microsoft.com/en-us/topic/december-10-2024-kb5048652-os-builds-19044-5247-and-19045-5247-454fbd4c-0723-449e-915b-8515ab41f8e3

    The KB articles have, for a long time, been uninformative. This one
    notes "This update addresses security issues for your Windows operating system" but give no details on what are the security issues.

    When I scroll down to the Improvements section, and click on "Windows 10 22H2" expandable section (since I don't have the LTSC edition, and
    probably don't, either),

    Correct. I don't.

    there is mention "Important: Use EKB KB5015684
    to update to Windows 10, version 22H2" which points to:

    https://support.microsoft.com/en-us/topic/kb5015684-featured-update-to-windows-10-version-22h2-by-using-an-enablement-package-09d43632-f438-47b5-985e-d6fd704eee61

    However, you're already at 22H2. Rather than use the unfriendly update
    log in Windows, I often resort to using Belarv Advisor. Easier to read,
    and I can search, too. At the bottom of the default page is a few of
    the hotfixes that have been installed (in past 90 days). Click on the
    "See all" link to get a list.

    https://www.belarc.com/products/belarc-advisor

    I've used Belarc before. It's trialware, I believe.

    Nirsoft also has their Windows Updates Viewer.

    https://www.nirsoft.net/utils/windows_updates_history_viewer.html

    That viewer doesn't provide a complete look at my history for some
    reason, and I've tried the options for listing updates. Nor does
    Nirsoft's "WinUpdatesList".

    Belarc can point out missing updates. Nirsoft can point out failed or
    aborted ones.

    Maybe so, but as I mentioned it doesn't work very well on my system for
    some reason.

    https://www.youtube.com/watch?v=5d5Ug0DUeo8
    44 patched vulnerabilities.
    36 are important.
    8 are critical: remote code execution vulnerabilities.
    Where did he get that info?

    Microsoft Update Catalog for KB5048652 https://www.catalog.update.microsoft.com/Search.aspx?q=5048652

    Seems like an important one then.

    Which one did you pick? The GDR (General Distribution Release) DU
    (Dynamic Update) ones require an Internet connect to their WSUS server.

    Thanks for clarifying that. The only version I've tried to install was
    this one:

    2024-12 Cumulative Update for Windows 10 Version 22H2 for x64-based
    Systems (KB5048652)
    Windows 10, version 1903 and later
    Security Updates
    12/10/2024
    n/a
    669.9 MB

    and it has failed each of the several times I've attempted to install it.

    I remember in Windows 7 that a failed update was often fixed by deleting
    the local update cache (C:\Windows\SoftwareDistribution\Download, delete everything underneath) to force the WU to rebuild its catalog. Haven't
    had to do that in Windows 10.

    I tried doing it (can't remember exactly how) but it made no difference.
    My update history was changed so that all failed attempt listings were
    removed though. New attempts to install the update and the resulting
    failures get added to the history though.

    https://www.minitool.com/news/kb5048652-not-installing.html

    That mentions running a Windows Update Troubleshooter.

    I ran that troubleshooter a few days ago. It took a long while and then
    gave me some advice, which I followed, but it didn't help install the
    update.

    Thanks very much for replying VanguardLH.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Mon Dec 23 13:42:26 2024
    "John C." <r9jmg0@yahoo.com> wrote:

    I've used Belarc before. It's trialware, I believe.

    There is a free personal-use license called Belarc Advisor for home use
    only. Business-use requires a paid commercial license for their
    BelManage product (https://www.belarc.com/products/belmanage) which is
    the enterprise version of Belarc Advisor with more features.

    Be careful of some of its suggestions as they can result in less
    functionality or even usability of your computer. One time, they
    suggested switching from SSL to FIPS for secure web communication, but
    that resulted in complete failure to connect to any HTTPS website.

    KB5048652 is a bitch for many users. Microsoft does not recommend to
    boot into Safe Mode to install updates as critical services may not be
    running to complete the update. In addition, Minitool mentions (https://www.minitool.com/news/can-you-install-windows-updates-in-safe-mode.html)
    that the update options are missing in Safe Mode. I would, however, do
    a selective startup to eliminate all startup programs, and make sure any 3rd-party antivirus program is disabled temporarily.

    https://www.minitool.com/news/fix-windows-update-error-0x8024000b.html

    That article suggest some things to try to resolve the 0x8024000b error.
    You already tried the first method: Windows Update Troubleshooter. As
    to how you cleared the cached update folder is unknown as yet.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store.
    You said you already tried to download and run the installer from the
    Microsoft Catalog site (looks like you picked the current one).

    You didn't use a tool or somehow manually disable Windows Update, right?
    Some tools will disable some features of Windows trying to increase your privacy or security, or just reduce the number of background network connections.

    Although not mentioned, you have since cold booted the computer, right?
    Not resume from [hybrid] hibnerate which resumes a prior Windows
    session, but fully shutdown Windows, power off, wait 10 seconds, and
    power on to do a fresh load of Windows.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Benutzer Zwei@21:1/5 to John C. on Mon Dec 23 23:58:43 2024
    On 20/12/2024 15:10, John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to overcome
    it and if so, would you please tell me how?

    TIA



    Have you tried deleting everything from SoftwareDistribution folder <C:\Windows\SoftwareDistribution> before trying to install the failed
    update? The files will be recreated when you reboot the system so there
    is nothing to worry about this.

    You will need to stop the Update service before you can delete some
    files from this folder.

    In my experience Microsoft updates are quite reliable these days but
    some users have deleted critical files because Manyama told them that
    Microsoft is spying. It is pure stupidity to delete any files from
    Windows operating system but we are living in a world where Biden was a one-term president and he suffered serious dementia while in office.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Benutzer Zwei on Tue Dec 24 01:45:57 2024
    On Mon, 12/23/2024 6:58 PM, Benutzer Zwei wrote:
    On 20/12/2024 15:10, John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to overcome
    it and if so, would you please tell me how?

    TIA



    Have you tried deleting everything from SoftwareDistribution folder <C:\Windows\SoftwareDistribution> before trying to install the failed
    update?

    No, don't do that.

    There is a whole procedure for doing that properly. It's a lengthy script
    and involved stopping four services, and there was something with permissions that needed to be adjusted. The script first appeared on an enthusiast
    site (a later version had improved error handling). Then Microsoft uses
    that script, as part of one of its troubleshooters. Can you imagine,
    just which Troubleshooter that might be ? The Troubleshooters (for as
    long as they continue to exist), can be located in Control Panels
    or perhaps some place like this.

    settings : system : troubleshooters : other_troubleshooters

    You can see some of the script details here. Don't just copy this one,
    because there is more than one version, and the error handling is better
    on some than others.

    https://answers.microsoft.com/en-us/windows/forum/all/how-toreset-windows-update-components-in-windows/14b86efd-1420-4916-9832-829125b1e8a3

    Part of the reason that script got written, is to stop people
    from "deleting everything from SoftwareDistribution" :-)

    The reference in the script, to smacking BITS upside the head,
    DoSVC does most of the work today. BITS continues to work, and
    it exists for compatibility. But all the care and attention
    in that script is (for the most part) not so necessary. It is
    possible, if you mess around with gpedit.msc, and a couple sets
    of policies, to "force" BITS to do all the work again, but that's
    not something normal people do to their computer. the conclusion
    you can reach from this observation, is nobody was tasked with
    keeping that script "fresh and up to date". I don't expect
    the version inside the Troubleshooter, is in any better shape.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Tue Dec 24 08:35:09 2024
    VanguardLH wrote:
    "John C." <r9jmg0@yahoo.com> wrote:

    I've used Belarc before. It's trialware, I believe.

    There is a free personal-use license called Belarc Advisor for home use
    only. Business-use requires a paid commercial license for their
    BelManage product (https://www.belarc.com/products/belmanage) which is
    the enterprise version of Belarc Advisor with more features.

    https://www.belarc.com/products/belarc-advisor

    On that page, there's a button named "Try for Free". Maybe the program
    is freeware and they aren't aware that their language is confusing.

    Regardless, I installed it and updated its security module. After it
    installed, it asked if I wanted it to create a profile of my system and
    I allowed it, because after all, that's the purpose of the program.

    It hung at 54% and after a while, I use the Task Manager to kill the
    process. Then I uninstalled the program.

    Be careful of some of its suggestions as they can result in less functionality or even usability of your computer. One time, they
    suggested switching from SSL to FIPS for secure web communication, but
    that resulted in complete failure to connect to any HTTPS website.

    Thanks, but I would never allow such a program to effect any changes on
    my computer.

    KB5048652 is a bitch for many users. Microsoft does not recommend to
    boot into Safe Mode to install updates as critical services may not be running to complete the update. In addition, Minitool mentions (https://www.minitool.com/news/can-you-install-windows-updates-in-safe-mode.html)
    that the update options are missing in Safe Mode. I would, however, do
    a selective startup to eliminate all startup programs, and make sure any 3rd-party antivirus program is disabled temporarily.

    https://www.minitool.com/news/fix-windows-update-error-0x8024000b.html

    That article suggest some things to try to resolve the 0x8024000b error.
    You already tried the first method: Windows Update Troubleshooter. As
    to how you cleared the cached update folder is unknown as yet.

    And worse yet, it seems to have messed things up because now the update
    history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next
    time I open the history, the entry is missing.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store.
    You said you already tried to download and run the installer from the Microsoft Catalog site (looks like you picked the current one).

    You didn't use a tool or somehow manually disable Windows Update, right?
    Some tools will disable some features of Windows trying to increase your privacy or security, or just reduce the number of background network connections.

    Although not mentioned, you have since cold booted the computer, right?
    Not resume from [hybrid] hibnerate which resumes a prior Windows
    session, but fully shutdown Windows, power off, wait 10 seconds, and
    power on to do a fresh load of Windows.

    I don't allow my computer) to run (and even turn off my cable modem and
    router when I'm not using it. This means that I always cold boot the
    computer whenever I intend to use it.

    Also, I loath hibernation and have disabled it. Even on my laptop.

    Microsoft assumes too much of its customers. I don't have two hours to
    squander every morning attempting (and failing) to correct this update
    failure. I am right at the cusp of moving to another OS. Another
    possibility is that I will convert to using two computers on a regular
    basis:

    1. A computer with basically only the OS and few installed programs that
    I'll use for accessing the internet

    2. A computer which will be completely air-gapped, has an older version
    of Windows (probably W7 or maybe even XP) and which never is allowed,
    under any circumstances, to go online.

    Windows 10 is a deplorable mess and I've thought this ever since I moved
    to it from Windows 7. And now, with the tricks they're pulling on the
    public in order to blackmail people into upgrading perfectly functional hardware in order to be able to go with the hated Windows 11, they're
    showing their true colors as the villainous bastards that they are.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Tue Dec 24 13:57:11 2024
    "John C." <r9jmg0@yahoo.com> wrote:

    And worse yet, it seems to have messed things up because now the update history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next
    time I open the history, the entry is missing.

    The cached update folder should get rebuilt. The reason to delete it
    was to force the dependency and supercede checking to rebuild a proper
    cache. After a reboot, did that folder get repopulated?

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store.

    Windows 10 is a deplorable mess and I've thought this ever since I moved
    to it from Windows 7.

    Was that a fresh install of Windows 10? Or did you drag tweaks and
    config changes from Windows 7 but upgrading from 7 to 10?

    Sounds more and more like you have a farked install that has more
    problems than just Windows Update. What you experience is not the norm.
    As mentioned in the Microsoft article, have you tried using System File Checker (sfc.exe) to repair the OS install?

    sfc /scannow

    If that fails, or in addition, have you used DISM to rebuild the OS with
    a known good fileset also mentioned in the Microsoft article? It
    mentions first running with /scanhealth, and then /checkhealth, but
    those are just checks and won't effect change until /restorehealth.

    DISM /Online /Cleanup-Image /RestoreHealth

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Bradshaw@21:1/5 to John C. on Tue Dec 24 12:31:30 2024
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to
    overcome it and if so, would you please tell me how?

    TIA

    I still think KB5001716 is the problem. I just noticed under Settings ->
    Apps & features this KB can be uninstalled. You could unistall it and try KB5048652 as a cumulative update. Or unnistall it and try to update over the internet. I know this is grasping for straws but that is usually where I
    end up. My KB5001716 is 8.94.00.
    --
    <Bill>

    Brought to you from Anchorage, Alaska

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Thu Dec 26 06:42:43 2024
    VanguardLH wrote:
    John C. wrote:

    And worse yet, it seems to have messed things up because now the update
    history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next
    time I open the history, the entry is missing.

    The cached update folder should get rebuilt. The reason to delete it
    was to force the dependency and supercede checking to rebuild a proper
    cache. After a reboot, did that folder get repopulated?

    Yes, it seems to have.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store.

    Windows 10 is a deplorable mess and I've thought this ever since I moved
    to it from Windows 7.

    Was that a fresh install of Windows 10? Or did you drag tweaks and
    config changes from Windows 7 but upgrading from 7 to 10?

    Sounds more and more like you have a farked install that has more
    problems than just Windows Update.

    I installed W10 Pro from scratch and did it according to MS guidelines.
    IOW, I didn't attempt any hacks to modify the installation.

    What you experience is not the norm.
    As mentioned in the Microsoft article, have you tried using System File Checker (sfc.exe) to repair the OS install?

    Yes, and it claimed to have successfully run:

    "Windows Resource Protection found corrupt files and successfully
    repaired them."

    However, I was still unable to install the update.

    sfc /scannow

    If that fails, or in addition, have you used DISM

    I did try to run DISM. Here is what happened:

    https://imgur.com/a/4FwNy4y

    You'll need to click on the image and magnify it.

    to rebuild the OS with
    a known good fileset also mentioned in the Microsoft article? It
    mentions first running with /scanhealth, and then /checkhealth, but
    those are just checks and won't effect change until /restorehealth.

    DISM /Online /Cleanup-Image /RestoreHealth

    See the above.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to John C. on Thu Dec 26 07:13:30 2024
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with the
    error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't help.
    I've also tried downloading the update from the Windows Update catalog
    and manually updating it, but that didn't work. Then I ran a DISC scan
    to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to overcome
    it and if so, would you please tell me how?

    TIA

    I may know what caused the problem now. Right before it started
    happening, my system told me that it getting updated and not to shut off
    the computer.

    Being in a hurry and after waiting entirely too long a period of time
    (about 15 or 20 minutes), I pressed and held the power button until the computer turned itself off.

    Pretty sure or at least it's a good guess that the update which was
    occurring when I turned off the computer was most likely KB5048652.
    Turning off the computer messed up some file or did something unpleasant otherwise, something which was necessary for KB5048652 to install.

    Fuck. >80(>

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bill Bradshaw@21:1/5 to John C. on Thu Dec 26 08:25:12 2024
    John C. wrote:
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with
    the error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't
    help. I've also tried downloading the update from the Windows Update
    catalog and manually updating it, but that didn't work. Then I ran a
    DISC scan to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to
    overcome it and if so, would you please tell me how?

    TIA

    I may know what caused the problem now. Right before it started
    happening, my system told me that it getting updated and not to shut
    off the computer.

    Being in a hurry and after waiting entirely too long a period of time
    (about 15 or 20 minutes), I pressed and held the power button until
    the computer turned itself off.

    Pretty sure or at least it's a good guess that the update which was
    occurring when I turned off the computer was most likely KB5048652.
    Turning off the computer messed up some file or did something
    unpleasant otherwise, something which was necessary for KB5048652 to
    install.

    Fuck. >80(>

    Did I read above that you did a reinstall of windows 10. That is what I did and I am now at KB5048652. I am dreading the next update.

    <Bill>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Bill Bradshaw on Thu Dec 26 12:27:59 2024
    Bill Bradshaw wrote:
    John C. wrote:
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with
    the error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't
    help. I've also tried downloading the update from the Windows Update
    catalog and manually updating it, but that didn't work. Then I ran a
    DISC scan to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to
    overcome it and if so, would you please tell me how?

    TIA

    I may know what caused the problem now. Right before it started
    happening, my system told me that it getting updated and not to shut
    off the computer.

    Being in a hurry and after waiting entirely too long a period of time
    (about 15 or 20 minutes), I pressed and held the power button until
    the computer turned itself off.

    Pretty sure or at least it's a good guess that the update which was
    occurring when I turned off the computer was most likely KB5048652.
    Turning off the computer messed up some file or did something
    unpleasant otherwise, something which was necessary for KB5048652 to
    install.

    Fuck. >80(>

    Did I read above that you did a reinstall of windows 10. That is what I did and I am now at KB5048652. I am dreading the next update.

    <Bill>

    Bill, I tried what you recommended (uninstalling KB5001716), but that
    didn't work either. And since then, I'm unable to remove the "Read only" attribute from my documents folder so that I can't edit any files there.

    At this point, I'm going to have to face up to the fact that I need to
    do a fresh install of Windows 10 because I hosed the existing
    installation. This means weeks and weeks of tweaking and reinstalling
    programs and drivers.

    As I said earlier, "Fuck".

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John C. on Thu Dec 26 19:02:34 2024
    On Thu, 12/26/2024 3:27 PM, John C. wrote:
    Bill Bradshaw wrote:
    John C. wrote:
    John C. wrote:
    I'm running 64 bit Windows 10 Pro, build 19045.5131, version 22H2.

    Update KB5048652 won't install, keeps downloading and failing with
    the error codes 0x8024000b and then later, 0x800f0831.


    I've installed the latest servicing stack update and that didn't
    help. I've also tried downloading the update from the Windows Update
    catalog and manually updating it, but that didn't work. Then I ran a
    DISC scan to restore my system's health, but that also didn't work.

    Anybody else run into this problem and if so, were you able to
    overcome it and if so, would you please tell me how?

    TIA

    I may know what caused the problem now. Right before it started
    happening, my system told me that it getting updated and not to shut
    off the computer.

    Being in a hurry and after waiting entirely too long a period of time
    (about 15 or 20 minutes), I pressed and held the power button until
    the computer turned itself off.

    Pretty sure or at least it's a good guess that the update which was
    occurring when I turned off the computer was most likely KB5048652.
    Turning off the computer messed up some file or did something
    unpleasant otherwise, something which was necessary for KB5048652 to
    install.

    Fuck. >80(>

    Did I read above that you did a reinstall of windows 10. That is what I did >> and I am now at KB5048652. I am dreading the next update.

    <Bill>

    Bill, I tried what you recommended (uninstalling KB5001716), but that
    didn't work either. And since then, I'm unable to remove the "Read only" attribute from my documents folder so that I can't edit any files there.

    At this point, I'm going to have to face up to the fact that I need to
    do a fresh install of Windows 10 because I hosed the existing
    installation. This means weeks and weeks of tweaking and reinstalling programs and drivers.

    As I said earlier, "Fuck".


    Do you have any backups or Restore Points
    that could modify the result ?

    I usually do a Safety Backup before major
    items like Repair Installs. A Safety Backup is
    a file you toss away after three or four days.
    By putting "ERASEME" in the filename, they can be
    left on the backup drive, until some space is needed
    and then they get "harvested" for the space they
    are taking.

    I don't do regular backups all that often, but
    I do have a "set" on the big backup drive right now.
    But just one set. The Safety backups are
    more focused, only an OS partition perhaps,
    and those take maybe 10-20 minutes. The data directories
    take a lot longer.

    On a 1TB drive, the 600GB chunk at the end, might
    get backed up every three months. The OS partitions,
    they would get a backup before an experiment.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to John C. on Thu Dec 26 18:46:56 2024
    "John C." <r9jmg0@yahoo.com> wrote:

    VanguardLH wrote:
    John C. wrote:

    And worse yet, it seems to have messed things up because now the update
    history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next >>> time I open the history, the entry is missing.

    The cached update folder should get rebuilt. The reason to delete it
    was to force the dependency and supercede checking to rebuild a proper
    cache. After a reboot, did that folder get repopulated?

    Yes, it seems to have.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store.

    Windows 10 is a deplorable mess and I've thought this ever since I moved >>> to it from Windows 7.

    Was that a fresh install of Windows 10? Or did you drag tweaks and
    config changes from Windows 7 but upgrading from 7 to 10?

    Sounds more and more like you have a farked install that has more
    problems than just Windows Update.

    I installed W10 Pro from scratch and did it according to MS guidelines.
    IOW, I didn't attempt any hacks to modify the installation.

    What you experience is not the norm.
    As mentioned in the Microsoft article, have you tried using System File
    Checker (sfc.exe) to repair the OS install?

    Yes, and it claimed to have successfully run:

    "Windows Resource Protection found corrupt files and successfully
    repaired them."

    However, I was still unable to install the update.

    sfc /scannow

    If that fails, or in addition, have you used DISM

    I did try to run DISM. Here is what happened:

    https://imgur.com/a/4FwNy4y

    You'll need to click on the image and magnify it.

    to rebuild the OS with
    a known good fileset also mentioned in the Microsoft article? It
    mentions first running with /scanhealth, and then /checkhealth, but
    those are just checks and won't effect change until /restorehealth.

    DISM /Online /Cleanup-Image /RestoreHealth

    See the above.

    I haven't needed to use an restore tools in Windows for a very long
    time. Instead I scheduled image backups, and restore from those.
    Easier to restore back to a prior known state than repair the unknown.
    Someone else will need to give info on where to point for the source
    files if not from an install drive where you ran setup.exe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to VanguardLH on Fri Dec 27 04:13:20 2024
    VanguardLH wrote:
    "John C." <r9jmg0@yahoo.com> wrote:

    VanguardLH wrote:
    John C. wrote:

    And worse yet, it seems to have messed things up because now the update >>>> history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next >>>> time I open the history, the entry is missing.

    The cached update folder should get rebuilt. The reason to delete it
    was to force the dependency and supercede checking to rebuild a proper
    cache. After a reboot, did that folder get repopulated?

    Yes, it seems to have.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store.

    Windows 10 is a deplorable mess and I've thought this ever since I moved >>>> to it from Windows 7.

    Was that a fresh install of Windows 10? Or did you drag tweaks and
    config changes from Windows 7 but upgrading from 7 to 10?

    Sounds more and more like you have a farked install that has more
    problems than just Windows Update.

    I installed W10 Pro from scratch and did it according to MS guidelines.
    IOW, I didn't attempt any hacks to modify the installation.

    What you experience is not the norm.
    As mentioned in the Microsoft article, have you tried using System File >>> Checker (sfc.exe) to repair the OS install?

    Yes, and it claimed to have successfully run:

    "Windows Resource Protection found corrupt files and successfully
    repaired them."

    However, I was still unable to install the update.

    sfc /scannow

    If that fails, or in addition, have you used DISM

    I did try to run DISM. Here is what happened:

    https://imgur.com/a/4FwNy4y

    You'll need to click on the image and magnify it.

    to rebuild the OS with
    a known good fileset also mentioned in the Microsoft article? It
    mentions first running with /scanhealth, and then /checkhealth, but
    those are just checks and won't effect change until /restorehealth.

    DISM /Online /Cleanup-Image /RestoreHealth

    See the above.

    I haven't needed to use an restore tools in Windows for a very long
    time. Instead I scheduled image backups, and restore from those.
    Easier to restore back to a prior known state than repair the unknown. Someone else will need to give info on where to point for the source
    files if not from an install drive where you ran setup.exe.

    It's all right, VanguardLH. You were very helpful. And now that I have
    the new problem of being unable to remove the "Read only" attribute from
    my "Documents" folder, it would appear that it's time for me to
    completely reinstall Windows, all my applications and drivers, and begin tweaking all over again. If this doesn't correct the situation, it will
    be time for my long affiliation with Windows and Microsoft to come to an
    end.

    MS has been engaging in feature degradation and other enshittifications
    of the Windows OS to where it takes far too much effort to keep it
    beaten into some kind of usable condition. Their loaded agendas of
    raping privacy and doing whatever it takes to maximize their profit have exceeded common sense at this point. They sees their relationship with
    end users as some kind of massive chess game instead of the productive partnership that it should be.

    Windows 11? Anybody who uses that version is only going to get more of
    the same. The other day, I read that use of that version is actually on
    the decline. It's that bad.

    A search on Microsoft's own "Bing" search engine shows this (from
    CoPilot, I believe):

    "Windows 11's market share has been declining worldwide, according to
    recent data from Statcounter. The operating system has stricter system requirements than Windows 10, including the need for a TPM 2.0 chip,
    which has prevented some users from upgrading. While Windows 11 has made
    some gains, Windows 10 is still dominating with a user base of 60.95%."

    I might even go back to Windows 7.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Paul on Fri Dec 27 04:32:19 2024
    Paul wrote:
    On Thu, 12/26/2024 3:27 PM, John C. wrote:
    Bill Bradshaw wrote:

    (snip)

    Bill, I tried what you recommended (uninstalling KB5001716), but that
    didn't work either. And since then, I'm unable to remove the "Read only"
    attribute from my documents folder so that I can't edit any files there.

    At this point, I'm going to have to face up to the fact that I need to
    do a fresh install of Windows 10 because I hosed the existing
    installation. This means weeks and weeks of tweaking and reinstalling
    programs and drivers.

    As I said earlier, "Fuck".

    Do you have any backups or Restore Points
    that could modify the result ?

    Good question. Yes, I have redundantly backed up my data although I did
    not do an image of my main drive. Regardless, I will be able to restore
    all my data without any problems.

    As for Restore points, yes, I have four of them going back to the 22nd. Unfortunately, the update install problem occurred before then.
    Regardless, I attempted to go back to the earliest on and the process
    failed, with System Restore locking up as the system attempted to
    restart. I had to (again) shut the system off by holding down the power
    button.

    I usually do a Safety Backup before major
    items like Repair Installs. A Safety Backup is
    a file you toss away after three or four days.
    By putting "ERASEME" in the filename, they can be
    left on the backup drive, until some space is needed
    and then they get "harvested" for the space they
    are taking.

    I don't do regular backups all that often, but
    I do have a "set" on the big backup drive right now.
    But just one set. The Safety backups are
    more focused, only an OS partition perhaps,
    and those take maybe 10-20 minutes. The data directories
    take a lot longer.

    On a 1TB drive, the 600GB chunk at the end, might
    get backed up every three months. The OS partitions,
    they would get a backup before an experiment.

    I was never able to find a decent freeware backup program that I could
    trust, so instead I depend on multiple, identical backups of things like:

    -my data
    -the start menu
    -my archive of freeware setup files
    -my enormous collection of portable software
    etc.

    A fresh install of Windows in the past never failed to correct any
    problems I was experiencing. That, however, given Microsoft's current
    track record, may have changed.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John C. on Fri Dec 27 11:42:22 2024
    On Fri, 12/27/2024 7:32 AM, John C. wrote:


    I was never able to find a decent freeware backup program that I could
    trust, so instead I depend on multiple, identical backups of things like:

    -my data
    -the start menu
    -my archive of freeware setup files
    -my enormous collection of portable software
    etc.

    A fresh install of Windows in the past never failed to correct any
    problems I was experiencing. That, however, given Microsoft's current
    track record, may have changed.


    Free ones:

    AOMEI Backupper
    Easeus has a backup program
    Macrium Reflect Free is backup/clone and so on.

    Acronis (payware) used to be good, when it was just a backup
    program, but the addition of an AV program and other
    Snake Oil sales-ware, ruined it.

    The free Seagate and Western Digital ("Branded") backup
    programs, are actually Acronis TrueImage and they work
    with a same-brand drive. The Seagate software works with a Seagate
    drive. The WDC version works with a WDC drive. The output
    would be a .tib file, just as Acronis is a .tib file.

    Many of the formats are "mount-able" as file systems
    on the PC.

    +-----+----------------+
    | MBR | Win10 C: |
    +-----+----------------+

    +-----+----------------+
    | MBR | Win10 K: | <=== Backup .tib mounts as virtual hard drive in Disk Management
    +-----+----------------+ <=== Backup .mring mounts as virtual hard drive in Disk Management

    You can copy a file from K: over to C: without doing
    a complete restore.

    Backup software is wonderful stuff. Get some :-)

    https://download.macrium.com/reflect/v7/v7.3.6391/reflect_setup_free_x64.exe

    There should also be a link floating around for an early free version 8. Whether that is
    still on their server, I do not know. At the current time, the freshest version of Macrium is available as TrialWare or as Payware. But the older free ones should
    be floating around. For the Macrium, there is a learning curve, and the amount of graphical detail can be disturbing to some.

    With one button, you can back up an entire PC with Macrium and put
    all the materials in one file. If the PC had three disks, all three
    disks can go in one .mrimg file. I usually do my backups in smaller
    chunks.

    *******

    The Windows 7 backup offered in W10/W11, you can do that from an
    Administrator terminal window. Items like "allCritical" can include
    EFS, Microsoft Reserved, C: , Recovery Partition. Further data partitions,
    like the D: and F: partition below, can also be included as separate items.
    The output is going onto the large E: drive external to the machine.

    wbAdmin start backup -backupTarget:E: -include:C:,D:,F: -allCritical -quiet

    There are many ways to have a Safety Backup salted away for later.
    It just needs space somewhere.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John C. on Fri Dec 27 12:02:35 2024
    On Fri, 12/27/2024 7:13 AM, John C. wrote:
    VanguardLH wrote:
    "John C." <r9jmg0@yahoo.com> wrote:

    VanguardLH wrote:
    John C. wrote:

    And worse yet, it seems to have messed things up because now the update >>>>> history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next >>>>> time I open the history, the entry is missing.

    The cached update folder should get rebuilt. The reason to delete it
    was to force the dependency and supercede checking to rebuild a proper >>>> cache. After a reboot, did that folder get repopulated?

    Yes, it seems to have.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store. >>>>>
    Windows 10 is a deplorable mess and I've thought this ever since I moved >>>>> to it from Windows 7.

    Was that a fresh install of Windows 10? Or did you drag tweaks and
    config changes from Windows 7 but upgrading from 7 to 10?

    Sounds more and more like you have a farked install that has more
    problems than just Windows Update.

    I installed W10 Pro from scratch and did it according to MS guidelines.
    IOW, I didn't attempt any hacks to modify the installation.

    What you experience is not the norm.
    As mentioned in the Microsoft article, have you tried using System File >>>> Checker (sfc.exe) to repair the OS install?

    Yes, and it claimed to have successfully run:

    "Windows Resource Protection found corrupt files and successfully
    repaired them."

    However, I was still unable to install the update.

    sfc /scannow

    If that fails, or in addition, have you used DISM

    I did try to run DISM. Here is what happened:

    https://imgur.com/a/4FwNy4y

    You'll need to click on the image and magnify it.

    to rebuild the OS with
    a known good fileset also mentioned in the Microsoft article? It
    mentions first running with /scanhealth, and then /checkhealth, but
    those are just checks and won't effect change until /restorehealth.

    DISM /Online /Cleanup-Image /RestoreHealth

    See the above.

    I haven't needed to use an restore tools in Windows for a very long
    time. Instead I scheduled image backups, and restore from those.
    Easier to restore back to a prior known state than repair the unknown.
    Someone else will need to give info on where to point for the source
    files if not from an install drive where you ran setup.exe.

    It's all right, VanguardLH. You were very helpful. And now that I have
    the new problem of being unable to remove the "Read only" attribute from
    my "Documents" folder, it would appear that it's time for me to
    completely reinstall Windows, all my applications and drivers, and begin tweaking all over again. If this doesn't correct the situation, it will
    be time for my long affiliation with Windows and Microsoft to come to an
    end.

    MS has been engaging in feature degradation and other enshittifications
    of the Windows OS to where it takes far too much effort to keep it
    beaten into some kind of usable condition. Their loaded agendas of
    raping privacy and doing whatever it takes to maximize their profit have exceeded common sense at this point. They sees their relationship with
    end users as some kind of massive chess game instead of the productive partnership that it should be.

    Windows 11? Anybody who uses that version is only going to get more of
    the same. The other day, I read that use of that version is actually on
    the decline. It's that bad.

    A search on Microsoft's own "Bing" search engine shows this (from
    CoPilot, I believe):

    "Windows 11's market share has been declining worldwide, according to
    recent data from Statcounter. The operating system has stricter system requirements than Windows 10, including the need for a TPM 2.0 chip,
    which has prevented some users from upgrading. While Windows 11 has made
    some gains, Windows 10 is still dominating with a user base of 60.95%."

    I might even go back to Windows 7.


    Did you have a failure when trying to *place* a file in Documents ?

    Be careful, with computers, to verify the failure is a functional failure,
    and not something discouraging shown in the graphics.

    Read Only doesn't actually mean Read Only by the way. Windows is not
    quite as "linear" as Linux/Unix permissions model, where fewer lies are involved.

    In my <cough> "Read Only" Documents folder, I was able to create
    a New Text File, change the name, open it as Test.txt in Notepad.
    Add some text to the file. *Save* the file. My Documents folder
    is in fact, "perfectly writeable" :-)

    Now, back to my Pizza Pocket.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Char Jackson@21:1/5 to Paul on Fri Dec 27 12:03:42 2024
    On Fri, 27 Dec 2024 11:42:22 -0500, Paul <nospam@needed.invalid> wrote:

    Acronis (payware) used to be good, when it was just a backup
    program, but the addition of an AV program and other
    Snake Oil sales-ware, ruined it.

    The free Seagate and Western Digital ("Branded") backup
    programs, are actually Acronis TrueImage and they work
    with a same-brand drive. The Seagate software works with a Seagate
    drive. The WDC version works with a WDC drive. The output
    would be a .tib file, just as Acronis is a .tib file.

    Casual readers might come away with the impression that the 'branded' versions of ATI only work with/on a same-brand drive, but that's not true. They work with
    any drive.

    When the program is launched and the drives are enumerated, the software needs to see a same-brand drive, but having found it, the software is fully unlocked and can then be used on any drive. The backup doesn't have to include the same-brand drive.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to Paul on Fri Dec 27 11:58:10 2024
    Paul <nospam@needed.invalid> wrote:

    Did you have a failure when trying to *place* a file in Documents ?

    Be careful, with computers, to verify the failure is a functional
    failure, and not something discouraging shown in the graphics.

    Read Only doesn't actually mean Read Only by the way. Windows is not
    quite as "linear" as Linux/Unix permissions model, where fewer lies
    are involved.

    In my <cough> "Read Only" Documents folder, I was able to create a
    New Text File, change the name, open it as Test.txt in Notepad. Add
    some text to the file. *Save* the file. My Documents folder is in
    fact, "perfectly writeable" :-)

    Read-only attribute on files is not the same as read-only attribute on
    folders. Read-only on a folder does NOT mean it is a read-only folder.

    To Windows, the read-only attribute on a folder means it is a special
    folder, like for a system folder or has a view customized by Windows (My Documents, Favorites, Fonts), or a folder whose view is customized
    (Documents, Pictures, Music, Videos) using the Properties -> Customize
    tab. When the read-only attribute is set on a folder, Explorer will
    read the desktop.ini file to check for special folder settings.

    https://support.microsoft.com/en-us/topic/you-cannot-view-or-change-the-read-only-or-the-system-attributes-of-folders-in-windows-server-2003-in-windows-xp-in-windows-vista-or-in-windows-7-55bd5ec5-d19e-6173-0df1-8f5b49247165

    That is how File Explorer handles the read-only attribute on folders.
    Other programs that interrogate the attributes on a folder may have
    their own skewed meanings which do not reflect how File Explorer handles
    the read-only and system attributes on a folder.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Paul on Fri Dec 27 13:02:04 2024
    Paul wrote:
    On Fri, 12/27/2024 7:13 AM, John C. wrote:
    VanguardLH wrote:
    "John C." <r9jmg0@yahoo.com> wrote:

    VanguardLH wrote:
    John C. wrote:

    And worse yet, it seems to have messed things up because now the update >>>>>> history won't add new items (like new installation failures of
    KB5048652.) It does this right after another attempt fails, but the next >>>>>> time I open the history, the entry is missing.

    The cached update folder should get rebuilt. The reason to delete it >>>>> was to force the dependency and supercede checking to rebuild a proper >>>>> cache. After a reboot, did that folder get repopulated?

    Yes, it seems to have.

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/update-management/error-0x800f0831-installing-update

    That one mentions using the DISM tool to repair the component store. >>>>>>
    Windows 10 is a deplorable mess and I've thought this ever since I moved >>>>>> to it from Windows 7.

    Was that a fresh install of Windows 10? Or did you drag tweaks and
    config changes from Windows 7 but upgrading from 7 to 10?

    Sounds more and more like you have a farked install that has more
    problems than just Windows Update.

    I installed W10 Pro from scratch and did it according to MS guidelines. >>>> IOW, I didn't attempt any hacks to modify the installation.

    What you experience is not the norm.
    As mentioned in the Microsoft article, have you tried using System File >>>>> Checker (sfc.exe) to repair the OS install?

    Yes, and it claimed to have successfully run:

    "Windows Resource Protection found corrupt files and successfully
    repaired them."

    However, I was still unable to install the update.

    sfc /scannow

    If that fails, or in addition, have you used DISM

    I did try to run DISM. Here is what happened:

    https://imgur.com/a/4FwNy4y

    You'll need to click on the image and magnify it.

    to rebuild the OS with
    a known good fileset also mentioned in the Microsoft article? It
    mentions first running with /scanhealth, and then /checkhealth, but
    those are just checks and won't effect change until /restorehealth.

    DISM /Online /Cleanup-Image /RestoreHealth

    See the above.

    I haven't needed to use an restore tools in Windows for a very long
    time. Instead I scheduled image backups, and restore from those.
    Easier to restore back to a prior known state than repair the unknown.
    Someone else will need to give info on where to point for the source
    files if not from an install drive where you ran setup.exe.

    It's all right, VanguardLH. You were very helpful. And now that I have
    the new problem of being unable to remove the "Read only" attribute from
    my "Documents" folder, it would appear that it's time for me to
    completely reinstall Windows, all my applications and drivers, and begin
    tweaking all over again. If this doesn't correct the situation, it will
    be time for my long affiliation with Windows and Microsoft to come to an
    end.

    MS has been engaging in feature degradation and other enshittifications
    of the Windows OS to where it takes far too much effort to keep it
    beaten into some kind of usable condition. Their loaded agendas of
    raping privacy and doing whatever it takes to maximize their profit have
    exceeded common sense at this point. They sees their relationship with
    end users as some kind of massive chess game instead of the productive
    partnership that it should be.

    Windows 11? Anybody who uses that version is only going to get more of
    the same. The other day, I read that use of that version is actually on
    the decline. It's that bad.

    A search on Microsoft's own "Bing" search engine shows this (from
    CoPilot, I believe):

    "Windows 11's market share has been declining worldwide, according to
    recent data from Statcounter. The operating system has stricter system
    requirements than Windows 10, including the need for a TPM 2.0 chip,
    which has prevented some users from upgrading. While Windows 11 has made
    some gains, Windows 10 is still dominating with a user base of 60.95%."

    I might even go back to Windows 7.


    Did you have a failure when trying to *place* a file in Documents ?

    Be careful, with computers, to verify the failure is a functional failure, and not something discouraging shown in the graphics.

    Read Only doesn't actually mean Read Only by the way. Windows is not
    quite as "linear" as Linux/Unix permissions model, where fewer lies are involved.

    In my <cough> "Read Only" Documents folder, I was able to create
    a New Text File, change the name, open it as Test.txt in Notepad.
    Add some text to the file. *Save* the file. My Documents folder
    is in fact, "perfectly writeable" :-)

    Now, back to my Pizza Pocket.

    Paul

    I should have done a better job of clarifying the problem. I was unable
    to modify and save any of the files in my documents folder. When I
    attempted to do this, I got various error messages depending on the
    program I was using to modify the file. I was, however, able to drag a
    copy of a file from a backup on another drive into the documents folder
    or subfolder and replace the original file with the backup.

    And right now, the problem has gone away like it did last night for me.
    I'm not holding my breath though, because the morning the problem had
    returned.

    VanguardLH's explanation (in MID <1nqnryf56dxw1$.dlg@v.nguard.lh>) of
    what a read only means to a folder vs a file was very enlightening though.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Paul on Fri Dec 27 13:15:16 2024
    Paul wrote:
    On Fri, 12/27/2024 7:32 AM, John C. wrote:


    I was never able to find a decent freeware backup program that I could
    trust, so instead I depend on multiple, identical backups of things like:

    -my data
    -the start menu
    -my archive of freeware setup files
    -my enormous collection of portable software
    etc.

    A fresh install of Windows in the past never failed to correct any
    problems I was experiencing. That, however, given Microsoft's current
    track record, may have changed.


    Free ones:

    AOMEI Backupper

    When I was using W7, this one hosed my system and made it so that
    Windows wouldn't open. They used to have a page on their website
    describing the problem, but I can't find it anymore. It took me days to
    find out that the problem was the program's ambakdrv.sys driver not
    wanting to load and which was causing Windows not to start.

    Not to worry though, I backed up the information at their page and it says: __________________________________________________________________________ Introduction:
    You may encounter a problem of loading driver ambakdrv.sys when you boot the Window from the cloned disk or from a new disk on which a
    system or disk backup image is restored.
    The problem might be because there is a conflict between ambakdrv.sys (a driver of AOMEI Backupper) and other drivers of the program.

    Aomei is unwilling to correct this problem, which started with versions
    after 4.6.1 (as far as I am aware).

    Solution:
    Create a WinPE bootable media with third-party WinPE tool on another computer, and then boot from the WinPE media to open registry to find
    and delete ambakdrv.
    Step 1: create the winpe bootable media and boot from the media.
    Step 2: open registry(Start--run "regedit").
    Step 3: find the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD......2092F}
    Step 4: delete "ambakdrv" value of UpperFilters.
    Step 5: find the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ambakdrv
    Step 6: delete the "ambakdrv".

    If there are still any problems, please contact our AOMEI Support Team: https://www.aomeitech.com/contact-us.html __________________________________________________________________________

    The program worked well and could back up a partition or drive, even a
    system drive. However, only the paid version would make that backup
    bootable.

    Easeus has a backup program

    Tried to use it on this computer last year and it wouldn't even start.

    Macrium Reflect Free is backup/clone and so on.

    Won't do incremental like Easeus claims to be able to do and (when it
    worked) like AOMEI Backupper was able to do.

    Acronis (payware) used to be good, when it was just a backup
    program, but the addition of an AV program and other
    Snake Oil sales-ware, ruined it.

    Ain't that often the way things go...

    The free Seagate and Western Digital ("Branded") backup
    programs, are actually Acronis TrueImage and they work
    with a same-brand drive. The Seagate software works with a Seagate
    drive. The WDC version works with a WDC drive. The output
    would be a .tib file, just as Acronis is a .tib file.

    Yeah, I've used them before like that. Don't think it will do
    incremental either though.

    Many of the formats are "mount-able" as file systems
    on the PC.

    +-----+----------------+
    | MBR | Win10 C: |
    +-----+----------------+

    +-----+----------------+
    | MBR | Win10 K: | <=== Backup .tib mounts as virtual hard drive in Disk Management
    +-----+----------------+ <=== Backup .mring mounts as virtual hard drive in Disk Management

    You can copy a file from K: over to C: without doing
    a complete restore.

    Backup software is wonderful stuff. Get some :-)

    https://download.macrium.com/reflect/v7/v7.3.6391/reflect_setup_free_x64.exe

    There should also be a link floating around for an early free version 8. Whether that is
    still on their server, I do not know. At the current time, the freshest version
    of Macrium is available as TrialWare or as Payware. But the older free ones should
    be floating around. For the Macrium, there is a learning curve, and the amount
    of graphical detail can be disturbing to some.

    With one button, you can back up an entire PC with Macrium and put
    all the materials in one file. If the PC had three disks, all three
    disks can go in one .mrimg file. I usually do my backups in smaller
    chunks.

    *******

    The Windows 7 backup offered in W10/W11, you can do that from an Administrator terminal window. Items like "allCritical" can include
    EFS, Microsoft Reserved, C: , Recovery Partition. Further data partitions, like the D: and F: partition below, can also be included as separate items. The output is going onto the large E: drive external to the machine.

    wbAdmin start backup -backupTarget:E: -include:C:,D:,F: -allCritical -quiet

    There are many ways to have a Safety Backup salted away for later.
    It just needs space somewhere.

    Well, my system has worked before, but as you can imagine it's a PITA.

    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John C. on Sat Dec 28 01:16:10 2024
    On Fri, 12/27/2024 4:15 PM, John C. wrote:
    Paul wrote:

    Free ones:

    AOMEI Backupper

    When I was using W7, this one hosed my system and made it so that
    Windows wouldn't open. They used to have a page on their website
    describing the problem, but I can't find it anymore. It took me days to
    find out that the problem was the program's ambakdrv.sys driver not
    wanting to load and which was causing Windows not to start.

    Not to worry though, I backed up the information at their page and it says: __________________________________________________________________________ Introduction:
    You may encounter a problem of loading driver ambakdrv.sys when you boot the Window from the cloned disk or from a new disk on which a
    system or disk backup image is restored.
    The problem might be because there is a conflict between ambakdrv.sys (a driver of AOMEI Backupper) and other drivers of the program.

    Aomei is unwilling to correct this problem, which started with versions
    after 4.6.1 (as far as I am aware).

    Solution:
    Create a WinPE bootable media with third-party WinPE tool on another computer, and then boot from the WinPE media to open registry to find
    and delete ambakdrv.
    Step 1: create the winpe bootable media and boot from the media.
    Step 2: open registry(Start--run "regedit").
    Step 3: find the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD......2092F}
    Step 4: delete "ambakdrv" value of UpperFilters.
    Step 5: find the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ambakdrv
    Step 6: delete the "ambakdrv".

    If there are still any problems, please contact our AOMEI Support Team: https://www.aomeitech.com/contact-us.html __________________________________________________________________________

    The program worked well and could back up a partition or drive, even a
    system drive. However, only the paid version would make that backup
    bootable.

    Easeus has a backup program

    Tried to use it on this computer last year and it wouldn't even start.

    Macrium Reflect Free is backup/clone and so on.

    Won't do incremental like Easeus claims to be able to do and (when it
    worked) like AOMEI Backupper was able to do.

    Acronis (payware) used to be good, when it was just a backup
    program, but the addition of an AV program and other
    Snake Oil sales-ware, ruined it.

    Ain't that often the way things go...

    The free Seagate and Western Digital ("Branded") backup
    programs, are actually Acronis TrueImage and they work
    with a same-brand drive. The Seagate software works with a Seagate
    drive. The WDC version works with a WDC drive. The output
    would be a .tib file, just as Acronis is a .tib file.

    Yeah, I've used them before like that. Don't think it will do
    incremental either though.

    Many of the formats are "mount-able" as file systems
    on the PC.

    +-----+----------------+
    | MBR | Win10 C: |
    +-----+----------------+

    +-----+----------------+
    | MBR | Win10 K: | <=== Backup .tib mounts as virtual hard drive in Disk Management
    +-----+----------------+ <=== Backup .mring mounts as virtual hard drive in Disk Management

    You can copy a file from K: over to C: without doing
    a complete restore.

    Backup software is wonderful stuff. Get some :-)

    https://download.macrium.com/reflect/v7/v7.3.6391/reflect_setup_free_x64.exe

    There should also be a link floating around for an early free version 8. Whether that is
    still on their server, I do not know. At the current time, the freshest version
    of Macrium is available as TrialWare or as Payware. But the older free ones should
    be floating around. For the Macrium, there is a learning curve, and the amount
    of graphical detail can be disturbing to some.

    With one button, you can back up an entire PC with Macrium and put
    all the materials in one file. If the PC had three disks, all three
    disks can go in one .mrimg file. I usually do my backups in smaller
    chunks.

    *******

    The Windows 7 backup offered in W10/W11, you can do that from an
    Administrator terminal window. Items like "allCritical" can include
    EFS, Microsoft Reserved, C: , Recovery Partition. Further data partitions, >> like the D: and F: partition below, can also be included as separate items. >> The output is going onto the large E: drive external to the machine.

    wbAdmin start backup -backupTarget:E: -include:C:,D:,F: -allCritical -quiet

    There are many ways to have a Safety Backup salted away for later.
    It just needs space somewhere.

    Well, my system has worked before, but as you can imagine it's a PITA.


    *************************************************************
    Seems to have a bunch of self-promotion HTML (not shown), so
    doesn't look like much of a free version.

    D:\TEMP>innounp_newer -x AOMEIBackupperStd_20241228.15790743.exe
    ; Version detected: 5500 (Unicode) (Custom)
    #1 {app}\CallbackCtrl.dll
    Reading slice D:\TEMP\AOMEIBackupperStd_20241228.15790743.exe
    #2 {app}\botva2.dll
    ...
    #398 {app}\QtCore4.dll
    #399 {app}\QtGui4.dll
    #400 {app}\QtNetwork4.dll
    #401 {app}\QtWebKit4.dll
    #402 {app}\QtXml4.dll
    #403 {app}\vcomp,2.dll
    #404 {app}\plugins\pe_dll_8_10\compatprovider.dll
    #405 {app}\plugins\pe_dll_8_10\dismapi.dll
    #406 {app}\plugins\pe_dll_8_10\dismcore.dll
    #407 {app}\plugins\pe_dll_8_10\dismcoreps.dll
    #408 {app}\plugins\pe_dll_8_10\dismprov.dll
    #409 {app}\plugins\pe_dll_8_10\ffuprovider.dll
    #410 {app}\plugins\pe_dll_8_10\folderprovider.dll
    #411 {app}\plugins\pe_dll_8_10\imagingprovider.dll
    #412 {app}\plugins\pe_dll_8_10\logprovider.dll
    #413 {app}\plugins\pe_dll_8_10\Microsoft.Dism.Powershell.dll
    #414 {app}\plugins\pe_dll_8_10\siloedpackageprovider.dll
    #415 {app}\plugins\pe_dll_8_10\ssshim.dll
    #416 {app}\plugins\pe_dll_8_10\vhdprovider.dll
    #417 {app}\plugins\pe_dll_8_10\wimgapi.dll
    #418 {app}\plugins\pe_dll_8_10\wimprovider.dll
    #419 {app}\plugins\pe_dll_xp_win7\dismapi.dll
    #420 {app}\plugins\pe_dll_xp_win7\ssshim.dll
    #421 {app}\plugins\pe_dll_xp_win7\wimgapi.dll
    #422 {app}\Version,1.ini
    #423 {app}\Version,2.ini
    #424 {win}\system32\ambakdrv,1.sys <=== They are still using it
    #425 {win}\system32\amwrtdrv,1.sys
    #426 {win}\system32\ammntdrv,1.sys
    #427 {win}\system32\amwrtdrv,2.sys
    #428 {win}\system32\ammntdrv,2.sys
    #429 {app}\driver\LoadDrv_Win32.exe
    #431 {app}\extend\adi,1.ico
    #432 {app}\extend\AMFileSystemParsing,1.dll
    #433 {app}\extend\Comn,1.dll
    #434 {app}\extend\Compress,1.dll
    ...
    #1032 install_script.iss

    *******

    The Easeus ToDo Backup seems to have a "teasing problem".
    First, an attempt to download, yields a 3MB stub downloader.

    Then you read a bit about how it behaves, and you'll likely stop right there.

    https://www.reddit.com/r/datarecovery/comments/mk2gxn/never_get_easeus_todo_backup/?rdt=34159

    *******

    You have to walk before you can fly.

    The purpose of Safety Backups is not to develop an Incremental Plan
    for all eternity. That's a site recovery plan with daily resolution,
    a more comprehensive plan.

    A safety Backup is just a "Full" which lasts for the duration of
    your other maintenance activity. It protects against an immediate
    catastrophe (broken OS, wiped-drive accident).

    I don't have any incrementals here, and my backup plan is
    a lot "looser" than your design. I'm making no claims my method
    is "better" -- it isn't. But I have "some" backups, and I have
    some percentage odds of restoring a boot-able configuration
    on deck in a reasonable period of time.

    *******

    A quick review of the other freebie, indicates it's not much of
    a deal. I have seen the Easeus teasing behavior before, so it is
    not out of line with the behavior of the company really.
    The AOMEI seems to have customization on a per-OS basis, but
    the "services" might well be a constant from one OS to the next.
    There are enough file flavors, they could likely do a different
    version for windows 7 versus Windows 11.

    The Macrium Free might offer Full and Differential, but not
    Incremental or Incremental-Forever. In the latter case, that
    one is supposed to take a Full and an attached Incremental Set
    and make a new Full by synthesis, and then more Incrementals
    are applied to the new Full. At some point, it does do
    a physical Full, before doing more Incrementals (to control for
    corruption possible from synthesizing too many things in a row).

    Summary: Instead of reaching "perfection" on the first try, you
    should instead start with a working "Full" method done
    on demand, as a "just in case". The idea is living life
    without saying the magic words "I guess I have to install
    from scratch".

    You can do a "Just in case" backup with dd.exe , if for
    example, you trusted absolutely none of that backup
    software. If we believed the Reddit thread, it might well
    be faster to do it the dd.exe way, than to wait
    for Easeus to tease you with your own files :-)

    But at least get some basic method available for
    usage at experiment time, so you have a cushion against
    accidents of one sort or another.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John C.@21:1/5 to Paul on Sat Dec 28 06:38:34 2024
    Paul wrote:

    (Snip)

    *************************************************************
    Seems to have a bunch of self-promotion HTML (not shown), so
    doesn't look like much of a free version.

    D:\TEMP>innounp_newer -x AOMEIBackupperStd_20241228.15790743.exe
    ; Version detected: 5500 (Unicode) (Custom)
    #1 {app}\CallbackCtrl.dll
    Reading slice D:\TEMP\AOMEIBackupperStd_20241228.15790743.exe
    #2 {app}\botva2.dll
    ...
    #398 {app}\QtCore4.dll
    #399 {app}\QtGui4.dll
    #400 {app}\QtNetwork4.dll
    #401 {app}\QtWebKit4.dll
    #402 {app}\QtXml4.dll
    #403 {app}\vcomp,2.dll
    #404 {app}\plugins\pe_dll_8_10\compatprovider.dll
    #405 {app}\plugins\pe_dll_8_10\dismapi.dll
    #406 {app}\plugins\pe_dll_8_10\dismcore.dll
    #407 {app}\plugins\pe_dll_8_10\dismcoreps.dll
    #408 {app}\plugins\pe_dll_8_10\dismprov.dll
    #409 {app}\plugins\pe_dll_8_10\ffuprovider.dll
    #410 {app}\plugins\pe_dll_8_10\folderprovider.dll
    #411 {app}\plugins\pe_dll_8_10\imagingprovider.dll
    #412 {app}\plugins\pe_dll_8_10\logprovider.dll
    #413 {app}\plugins\pe_dll_8_10\Microsoft.Dism.Powershell.dll
    #414 {app}\plugins\pe_dll_8_10\siloedpackageprovider.dll
    #415 {app}\plugins\pe_dll_8_10\ssshim.dll
    #416 {app}\plugins\pe_dll_8_10\vhdprovider.dll
    #417 {app}\plugins\pe_dll_8_10\wimgapi.dll
    #418 {app}\plugins\pe_dll_8_10\wimprovider.dll
    #419 {app}\plugins\pe_dll_xp_win7\dismapi.dll
    #420 {app}\plugins\pe_dll_xp_win7\ssshim.dll
    #421 {app}\plugins\pe_dll_xp_win7\wimgapi.dll
    #422 {app}\Version,1.ini
    #423 {app}\Version,2.ini
    #424 {win}\system32\ambakdrv,1.sys <=== They are still using it
    #425 {win}\system32\amwrtdrv,1.sys
    #426 {win}\system32\ammntdrv,1.sys
    #427 {win}\system32\amwrtdrv,2.sys
    #428 {win}\system32\ammntdrv,2.sys
    #429 {app}\driver\LoadDrv_Win32.exe
    #431 {app}\extend\adi,1.ico
    #432 {app}\extend\AMFileSystemParsing,1.dll
    #433 {app}\extend\Comn,1.dll
    #434 {app}\extend\Compress,1.dll
    ...
    #1032 install_script.iss

    *******

    The Easeus ToDo Backup seems to have a "teasing problem".
    First, an attempt to download, yields a 3MB stub downloader.

    Then you read a bit about how it behaves, and you'll likely stop right there.

    https://www.reddit.com/r/datarecovery/comments/mk2gxn/never_get_easeus_todo_backup/?rdt=34159

    *******

    You have to walk before you can fly.

    The purpose of Safety Backups is not to develop an Incremental Plan
    for all eternity. That's a site recovery plan with daily resolution,
    a more comprehensive plan.

    A safety Backup is just a "Full" which lasts for the duration of
    your other maintenance activity. It protects against an immediate
    catastrophe (broken OS, wiped-drive accident).

    I don't have any incrementals here, and my backup plan is
    a lot "looser" than your design. I'm making no claims my method
    is "better" -- it isn't. But I have "some" backups, and I have
    some percentage odds of restoring a boot-able configuration
    on deck in a reasonable period of time.

    *******

    A quick review of the other freebie, indicates it's not much of
    a deal. I have seen the Easeus teasing behavior before, so it is
    not out of line with the behavior of the company really.
    The AOMEI seems to have customization on a per-OS basis, but
    the "services" might well be a constant from one OS to the next.
    There are enough file flavors, they could likely do a different
    version for windows 7 versus Windows 11.

    The Macrium Free might offer Full and Differential, but not
    Incremental or Incremental-Forever. In the latter case, that
    one is supposed to take a Full and an attached Incremental Set
    and make a new Full by synthesis, and then more Incrementals
    are applied to the new Full. At some point, it does do
    a physical Full, before doing more Incrementals (to control for
    corruption possible from synthesizing too many things in a row).

    Summary: Instead of reaching "perfection" on the first try, you
    should instead start with a working "Full" method done
    on demand, as a "just in case". The idea is living life
    without saying the magic words "I guess I have to install
    from scratch".

    You can do a "Just in case" backup with dd.exe , if for
    example, you trusted absolutely none of that backup
    software. If we believed the Reddit thread, it might well
    be faster to do it the dd.exe way, than to wait
    for Easeus to tease you with your own files :-)

    But at least get some basic method available for
    usage at experiment time, so you have a cushion against
    accidents of one sort or another.

    Currently, I'm using SyncBackFree:

    https://www.2brightsparks.com/download-syncbackfree.html

    I have many backup profiles listed in that program, and can run them at
    the same time. Each profile backs up a specific folder, partition or
    drive. However, the program can't do shadow copies AFAIK. Thus, I use it
    only to back up my data.

    This is the system I currently use.


    --
    John C.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to John C. on Sat Dec 28 14:18:23 2024
    On Sat, 12/28/2024 9:38 AM, John C. wrote:


    Currently, I'm using SyncBackFree:

    https://www.2brightsparks.com/download-syncbackfree.html

    I have many backup profiles listed in that program, and can run them at
    the same time. Each profile backs up a specific folder, partition or
    drive. However, the program can't do shadow copies AFAIK. Thus, I use it
    only to back up my data.

    This is the system I currently use.

    Good backup tools, come with a "boot CD".

    The boot CD is based on WinPE (Windows Preinstall Environment),
    an environment not intended for running programs as such. But which
    is definitely used, to do just that. It is used sort of like a
    kiosk OS, only without the absolute shackles that kiosk OSes have.

    A lot of the backup/clone programs, have the emergency boot disc.
    The emergency boot disc is based on the WADK kit for various OSes.
    A WinPE5 or WinPE10 kit, has USB3 drivers, necessary for usage of
    any decent-speed external drives. with a suitable "construction kit"
    provided with the Backup/Clone program, even additional drivers
    not in Windows, can be added to the image. I could add that Intel
    NIC no one has a driver for, on the other machine.

    The Macrium Rescue CD, can do a backuo to a file share on my other
    machine. The only target is not an external disk drive. You can
    use a share or a NAS for a backup. I sometimes use the RAMDrive
    on a second machine, as the place for the output of a quick backup.

    If a backup is made from the emergency boot disc, it does not
    use VSS (because WinPE does not actually have VSS). Since all the
    hard drive partitions are at rest, when the X: partition boots
    from the CD, you can make perfect copies of your C: drive
    from there. It does not need VSS to make perfect copies of the C: .

    If you were concerned about the thoroughness of a non-VSS attempt
    to back up C: , that is when you reach for the emergency boot CD.

    If you were clever, you could even find a way to load 2brightsparks
    to a 32-bit WinPE based disc and run it from there. While booted from
    the CD X: drive, you can back up C: with the program. It is important
    to use a 32-bit WinPE disc, and use a 32-bit version of 2brightsparks.
    There is a small probability the combo might work (no guarantees).

    The emergency boot CD can do backups, restores, clones. It's
    more or less fully functional for basic operations. I would
    have to own the commercial version, to understand just what scripts
    would not run from a CD based version of a tool.

    Some things are just limitless fun.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)