• Re: chkdsk finds errors, fails to correct them

    From Carlos E.R.@3:633/280.2 to All on Fri Aug 1 10:41:12 2025
    On 2025-07-31 23:09, Paul wrote:
    On Thu, 7/31/2025 1:04 PM, Jason wrote:
    Now and again, I run chkdsk on partitions to look for
    trouble. Lately, on C:, chkdsk reports bitmap errors and
    asks if I want to restart to fix them offline. I do that
    but chkdsk again reports errors upon restarting. This
    happened three times in a row. What's up and should I
    worry? BTW, C: is a 1G SSD should that make any
    difference.


    As you know, Microsoft on the one hand, claims the NTFS API
    has not changed in years, thus "everything is compatible"
    as they spin their new OSes. They refuse to change the NTFS
    release number.

    But, changes have been made, and they "aren't exactly compatible".
    A glaring example, is the ability to make 2MB clusters in W10/W11,
    which Windows 7 cannot read.

    There is another I can't remember... ah, "reparse points", you mentioned
    it later. Affects compressed directories, I think. Linux has problems
    with them.



    --
    Cheers, Carlos.

    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Fri Aug 1 13:22:22 2025
    On Thu, 7/31/2025 8:41 PM, Carlos E.R. wrote:
    On 2025-07-31 23:09, Paul wrote:
    On Thu, 7/31/2025 1:04 PM, Jason wrote:
    Now and again, I run chkdsk on partitions to look for
    trouble. Lately, on C:, chkdsk reports bitmap errors and
    asks if I want to restart to fix them offline. I do that
    but chkdsk again reports errors upon restarting. This
    happened three times in a row. What's up and should I
    worry? BTW, C: is a 1G SSD should that make any
    difference.


    As you know, Microsoft on the one hand, claims the NTFS API
    has not changed in years, thus "everything is compatible"
    as they spin their new OSes. They refuse to change the NTFS
    release number.

    But, changes have been made, and they "aren't exactly compatible".
    A glaring example, is the ability to make 2MB clusters in W10/W11,
    which Windows 7 cannot read.

    There is another I can't remember... ah, "reparse points", you mentioned it later. Affects compressed directories, I think. Linux has problems with them.


    That's how Microsoft ensures that Linux never catches up :-)

    I'm sure they don't do this on purpose. It's just an accident or something.

    Paul



    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Fri Aug 1 19:39:42 2025
    In article <106gcs2$3tvqc$2@dont-email.me>, T@invalid.invalid says...


    As administrator, try running system file check:
    sfc /scannow


    I rarely got SFC to work, until I learned that it's often necessary to
    run DISM first.

    Essentially, SFC compares files in the running system with those salted
    away in the Component Store, and replaces any which are found corrupt.
    But the Component Store itself can become corrupt, and DISM fixes that.

    I run DISM /Online /Cleanup-Image /ScanHealth
    If this "verificaton" produces no errors, then I run SFC /Scannow

    If DISM ... /ScanHealth does come back with errors, then I run:
    DISM /Online /Cleanup-Image /RestoreHealth
    .... which copies down fresh versions of Component Store items from the
    web.

    If that doesn't work (happened once to me) then there's a process for rebuilding the Component Store from a downloaded image.

    Since I found out about DISM (which also does heaps of things I don't
    really understand!) SFC has suprisingly often reported that it has
    repaired corrupted files, and glitches have been seen to go.


    --
    Phil, London

    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Fri Aug 1 22:03:53 2025
    On Fri, 8/1/2025 5:39 AM, Philip Herlihy wrote:
    In article <106gcs2$3tvqc$2@dont-email.me>, T@invalid.invalid says...


    As administrator, try running system file check:
    sfc /scannow


    I rarely got SFC to work, until I learned that it's often necessary to
    run DISM first.

    Essentially, SFC compares files in the running system with those salted
    away in the Component Store, and replaces any which are found corrupt.
    But the Component Store itself can become corrupt, and DISM fixes that.

    I run DISM /Online /Cleanup-Image /ScanHealth
    If this "verificaton" produces no errors, then I run SFC /Scannow

    If DISM ... /ScanHealth does come back with errors, then I run:
    DISM /Online /Cleanup-Image /RestoreHealth
    ... which copies down fresh versions of Component Store items from the
    web.

    If that doesn't work (happened once to me) then there's a process for rebuilding the Component Store from a downloaded image.

    Since I found out about DISM (which also does heaps of things I don't
    really understand!) SFC has suprisingly often reported that it has
    repaired corrupted files, and glitches have been seen to go.


    --
    Phil, London


    Like building a house, the two tools are in their own "layers".

    DISM is the foundation of the house. If you're building a house,
    you do your DISM first.

    SFC is the room above that (keeps the system files and the
    windows file protection cache aligned). The files that the
    system uses, are linked to the WinSXS thing which is maintained
    by DISM.

    When you install the OS, you don't install the OS, you
    "install a thousand packages". And together, once linked
    to various places, that functions as an OS. The purpose
    of describing it that way, is to point out it is "modular"
    and by changing the package set or changing or removing
    some linkages, a more streamlined OS could result.

    When you get a Patch Tuesday file, those are Jumbo installers
    with multiple package changes inside. And doing it that way,
    apparently helps hide the broken nature of Windows Update
    and its implementation. The smaller "security packages" in
    the past, seemed to make Windows Update slower to calculate
    what was needed in the way of patches. The Jumbo installers
    are still requiring a lot of "computation", but at least it
    is now pretty obvious how many packages should come in on
    Patch Tuesday (anywhere from zero to three, one or two being
    more common). The two package case, is a dotNET update and
    a security package (the security package consisting of two
    parts, and the second part is a Servicing Stack Update that
    comes in each month now).

    You would be surprised sometimes, at HOW the work is being
    done. I assumed SFC disk activity, that was "reads" and it
    was analyzing the stuff. Instead, if you check, you might
    find it is doing "unconditional writes" and it doesn't
    really "check" anything, it "paves instead". Check with ProcMon
    and see what it is doing.

    Paul

    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Carlos E.R.@3:633/280.2 to All on Fri Aug 1 22:18:17 2025
    On 2025-08-01 05:22, Paul wrote:
    On Thu, 7/31/2025 8:41 PM, Carlos E.R. wrote:
    On 2025-07-31 23:09, Paul wrote:
    On Thu, 7/31/2025 1:04 PM, Jason wrote:
    Now and again, I run chkdsk on partitions to look for
    trouble. Lately, on C:, chkdsk reports bitmap errors and
    asks if I want to restart to fix them offline. I do that
    but chkdsk again reports errors upon restarting. This
    happened three times in a row. What's up and should I
    worry? BTW, C: is a 1G SSD should that make any
    difference.


    As you know, Microsoft on the one hand, claims the NTFS API
    has not changed in years, thus "everything is compatible"
    as they spin their new OSes. They refuse to change the NTFS
    release number.

    But, changes have been made, and they "aren't exactly compatible".
    A glaring example, is the ability to make 2MB clusters in W10/W11,
    which Windows 7 cannot read.

    There is another I can't remember... ah, "reparse points", you mentioned it later. Affects compressed directories, I think. Linux has problems with them.


    That's how Microsoft ensures that Linux never catches up :-)

    I'm sure they don't do this on purpose. It's just an accident or something.

    <https://www.genbeta.com/actualidad/microsoft-bloqueo-correo-desarrollador-libreoffice-al-intentar-buscar-solucion-se-encontro-sistema-desfasado>


    Microsoft blocked the email account of a LibreOffice developer. When
    trying to find a solution, he encountered an outdated system.
    Microsoft's support system was unable to provide an effective solution.

    The already tense relationship between Microsoft and the LibreOffice community, the main open-source alternative to Office, may have added a
    new and frustrating chapter. Mike Kaganski, a developer of the free
    office suite, discovered this week that his Microsoft account had been suddenly blocked without a clear explanation. Worst of all, he only
    noticed the block when he was about to send an email to the project's developer list.

    Microsoft's warning message was as brief as it was alarming: his account
    had been blocked for violating the terms of service. Kaganski, truly surprised, went so far as to publicly invite anyone to look at his email
    and try to detect any messages that were out of the ordinary, as most of
    them were technical messages about the development of LibreOffice.

    Translated with DeepL.com (free version)


    I understand this chap is a Libre Office contributor, in Windows.



    --
    Cheers, Carlos.

    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Jason@3:633/280.2 to All on Sat Aug 2 08:16:30 2025
    In article <106gcs2$3tvqc$2@dont-email.me>,
    T@invalid.invalid says...

    On 7/31/25 10:44 AM, jason_warren wrote:
    In article <106g9ub$3tvqc$1@dont-email.me>,
    T@invalid.invalid says...

    On 7/31/25 10:04 AM, Jason wrote:
    Now and again, I run chkdsk on partitions to look for
    trouble. Lately, on C:, chkdsk reports bitmap errors and
    asks if I want to restart to fix them offline. I do that
    but chkdsk again reports errors upon restarting. This
    happened three times in a row. What's up and should I
    worry? BTW, C: is a 1G SSD should that make any
    difference.



    What does Crystal Disk Info say about your SSD drive?

    https://sourceforge.net/projects/crystaldiskinfo/
    https://sourceforge.net/projects/crystaldiskinfo/files/

    I didn't mention it, but I did run Crystal Disk too. It
    says all is well...

    Probably (note the weasel word) nothing wrong then.

    What chkdsk command did you run? "chkdsk /f"?
    The error you are getting may also be bogus.

    As administrator, try running system file check:
    sfc /scannow

    sfc -did- find some problems and fixed them but not until
    I ran it a second time. Now the CBS log is clean.

    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Carlos E.R.@3:633/280.2 to All on Sat Aug 2 22:20:10 2025
    On 2025-08-02 02:30, T wrote:
    On 8/1/25 5:18 AM, Carlos E.R. wrote:
    Microsoft blocked the email account of a LibreOffice developer. When
    trying to find a solution, he encountered an outdated system.
    Microsoft's support system was unable to provide an effective solution.

    The already tense relationship between Microsoft and the LibreOffice
    community, the main open-source alternative to Office, may have added
    a new and frustrating chapter. Mike Kaganski, a developer of the free
    office suite, discovered this week that his Microsoft account had been
    suddenly blocked without a clear explanation. Worst of all, he only
    noticed the block when he was about to send an email to the project's
    developer list.

    Microsoft's warning message was as brief as it was alarming: his
    account had been blocked for violating the terms of service. Kaganski,
    truly surprised, went so far as to publicly invite anyone to look at
    his email and try to detect any messages that were out of the
    ordinary, as most of them were technical messages about the
    development of LibreOffice.

    Translated with DeepL.com (free version)


    I understand this chap is a Libre Office contributor, in Windows.


    Not to ask too stupid a question, but did he change his
    eMail carrier after that?

    I wonder why he was using a M$ spyware account to
    start with? I set up all my Windows users with
    off line accounts.

    No idea. Maybe because he has to ask support questions in order to do
    his job on LO.

    --
    Cheers, Carlos.

    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: ---:- FTN<->UseNet Gate -:--- (3:633/280.2@fidonet)
  • From Hank Rogers@3:633/280.2 to All on Mon Aug 4 17:53:20 2025
    T <T@invalid.invalid> wrote:
    On 8/2/25 5:20 AM, Carlos E.R. wrote:
    Not to ask too stupid a question, but did he change his
    eMail carrier after that?

    I wonder why he was using a M$ spyware account to
    start with? I set up all my Windows users with
    off line accounts.

    No idea. Maybe because he has to ask support questions in order to do
    his job on LO.


    In all my years, I will only post on M$ support forums
    when I am desperate. I have yet to have them actually
    answer one of my questions. They cut and paste some
    marketing approved drivel then have the guts to sent
    me a request asking for complements over their service.


    That’s about the same as my experience. Rarely do I see a response that answers people’s questions.




    --- MBSE BBS v1.1.2 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)