• Re: Window 11 external drive compatability with Win7?

    From pyotr filipivich@3:633/10 to All on Wednesday, September 23, 2026 18:06:59
    Arkadiusz 'Black Fox' Artyszuk <asdfadsasdfa@atomicmail.io> on Sat, 19
    Sep 2026 09:53:29 +0200 typed in alt.comp.os.windows-11 the
    following:
    pyotr13315@yahoo.com wrote:

    That's the issue
    I have a windows 7 box which I've used "forever" I have an external
    SSD drive "J", which gets a copy of all my data files.
    Which is then plugged into the Laptop (running Win 11 Home (S)*) so I
    can do those things which can no longer be done on the obsolete box.
    Banking, reading email, shopping.
    Logoff laptop,
    shut down laptop.
    wait a few extra minutes.
    Unplug Drive J.
    Plug drive J into Win7 box.
    "Do you want to scan drive J for errors?" resulting from an improper
    device removal.
    Every single time.

    Simply logging off or shutting down doesn't always guarantee immediate
    cache flushing for external USB storage devices.
    Possible solutions / workarounds:
    1. Before shutting down or unplugging the drive from the Windows 11
    laptop, look at the system tray, click the Safely Remove Hardware and
    eject drive J. Always wait for "Safe to Remove Hardware" notification
    before physically unplugging it.
    This was where I seriously hit a problem.
    Microsoft cannot eject the disk as {some unnamed} process is
    accessing it.

    2. Disable Fast Startup on Windows 11 in this case. Fast Startup
    prevents Windows 11 from fully shutting down, which can keep external
    drives locked in a semi-mounted state.

    Will check this next time. Explains a lot.

    3. Change the removal policy of external storage devices in Windows 11
    to "Quick removal" if it is somehow set to "Better performance".
    I hope something helps.

    Will try that too.


    --
    pyotr filipivich
    This Week's Panel: Us & Them - Eliminating Them.
    Next Month's Panel: Having eliminated the old Them(tm)
    Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Ramanujan's Summation@3:633/10 to All on Thursday, September 24, 2026 17:59:11
    On 24/09/2026 02:06, pyotr filipivich wrote:
    This was where I seriously hit a problem.
    Microsoft cannot eject the disk as {some unnamed} process is
    accessing it.

    The easiest way to resolve this issue is to log out of your account and
    log back in. You should then be able to eject the disk without any problems.

    When you log out of the account, any processes initiated by the user are automatically stopped, including those accessing the disk.

    HTH






    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Frank Slootweg@3:633/10 to All on Friday, September 25, 2026 18:27:36
    Ramanujan's Summation <rs@invalid.invalid> wrote:
    On 24/09/2026 02:06, pyotr filipivich wrote:
    This was where I seriously hit a problem.
    Microsoft cannot eject the disk as {some unnamed} process is accessing it.

    The easiest way to resolve this issue is to log out of your account and
    log back in. You should then be able to eject the disk without any problems.

    When you log out of the account, any processes initiated by the user are automatically stopped, including those accessing the disk.

    Maybe yes, maybe no. For example Windows' indexing process is all too
    happy to touch a disk, even if it has been told not to index it.

    Bottom line: 'Eject' works or it doesn't.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From pyotr filipivich@3:633/10 to All on Friday, September 25, 2026 15:34:57
    Ramanujan's Summation<rs@invalid.invalid> on Thu, 24 Sep 2026 17:59:11
    +0100 typed in alt.comp.os.windows-11 the following:
    On 24/09/2026 02:06, pyotr filipivich wrote:
    This was where I seriously hit a problem.
    Microsoft cannot eject the disk as {some unnamed} process is
    accessing it.

    The easiest way to resolve this issue is to log out of your account and
    log back in. You should then be able to eject the disk without any problems.

    When you log out of the account, any processes initiated by the user are >automatically stopped, including those accessing the disk.

    HTH

    thanks, that makes some sort of sense, I'm sure.


    --
    pyotr filipivich
    This Week's Panel: Us & Them - Eliminating Them.
    Next Month's Panel: Having eliminated the old Them(tm)
    Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)