• An upgrade problem

    From John Hill@watcombeman@yahoo.co.uk to uk.comp.sys.mac on Sat Sep 20 07:59:05 2025
    From Newsgroup: uk.comp.sys.mac

    My eldest son is attempting to upgrade Sequoia running on VMware on Windows
    11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade is done, it knows his name, but does not accept his password.

    Any suggestions as to why this should happen? One was that he would have to turn FileVault off before upgrading, but when he checked, FileVault was
    already off so that was not the problem.

    His technical competence far exceeds mine (before he retired he was Mr Fixit for supercomputers) but is limited to Windows, Linux, Android, Raspberry Pi
    ant the like. He is experimenting with MacOS because I, his brother snd his sister are all Mac users.

    Old John.
    --
    Vita non est vivere sed valere vita est
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From David B.@BD@hotmail.co.uk to uk.comp.sys.mac on Sat Sep 20 09:46:35 2025
    From Newsgroup: uk.comp.sys.mac

    On 20/09/2025 08:59, John Hill wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade is done, it knows his name, but does not accept his password.

    Any suggestions as to why this should happen? One was that he would have to turn FileVault off before upgrading, but when he checked, FileVault was already off so that was not the problem.

    His technical competence far exceeds mine (before he retired he was Mr Fixit for supercomputers) but is limited to Windows, Linux, Android, Raspberry Pi ant the like. He is experimenting with MacOS because I, his brother snd his sister are all Mac users.


    Hello again Old John! I asked my friend 'Claude' and this is his AI answer:-

    =

    This is a common and frustrating issue when upgrading macOS in a VM environment. Here are the most likely causes and solutions:
    Most Common Causes:

    Keychain corruption during VM upgrade - The macOS keychain can get
    corrupted when running in VMware, especially during major OS upgrades
    User account database issues - The upgrade process sometimes corrupts
    the local user database in virtualized environments
    VMware Tools compatibility - Outdated or incompatible VMware Tools can interfere with authentication after upgrades

    Suggested Solutions (in order of likelihood to work):

    Reset password from Recovery Mode:

    Boot into Recovery Mode (hold Cmd+R during startup)
    Go to Utilities > Terminal
    Type: resetpassword and follow the prompts
    This often fixes corrupted authentication without losing data


    Create a new admin user temporarily:

    From Recovery Mode terminal: dscl . -create /Users/newadmin
    Set up the new user as admin, log in, then fix the original account


    Check VMware Tools:

    Ensure VMware Tools are updated to the latest version compatible with
    Sequoia
    Sometimes uninstalling/reinstalling VMware Tools after the OS upgrade helps


    Safe Mode login:

    Try booting in Safe Mode (hold Shift) to see if he can log in there



    Given his technical background, he'll probably be comfortable with the Terminal approach. The password reset from Recovery Mode is usually the quickest fix for this specific issue.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Alan B@alanrichardbarker@gmail.com.invalid to uk.comp.sys.mac on Sat Sep 20 09:30:41 2025
    From Newsgroup: uk.comp.sys.mac

    On 2025-09-20, John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade is done, it knows his name, but does not accept his password.

    Any suggestions as to why this should happen? One was that he would have to turn FileVault off before upgrading, but when he checked, FileVault was already off so that was not the problem.

    His technical competence far exceeds mine (before he retired he was Mr Fixit for supercomputers) but is limited to Windows, Linux, Android, Raspberry Pi ant the like. He is experimenting with MacOS because I, his brother snd his sister are all Mac users.

    Please be aware that running macOS on anything other than Apple hardware breaks the SLA:

    <https://www.apple.com/legal/sla/docs/macOSTahoe.pdf>

    As discussed on the Support forums:

    <https://discussions.apple.com/thread/250646417?sortBy=rank>
    --
    Cheers, Alan
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From David B.@BD@hotmail.co.uk to uk.comp.sys.mac on Sat Sep 20 11:46:32 2025
    From Newsgroup: uk.comp.sys.mac

    On 20/09/2025 10:30, Alan B wrote:
    On 2025-09-20, John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >> 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade
    is done, it knows his name, but does not accept his password.

    Any suggestions as to why this should happen? One was that he would have to >> turn FileVault off before upgrading, but when he checked, FileVault was
    already off so that was not the problem.

    His technical competence far exceeds mine (before he retired he was Mr Fixit >> for supercomputers) but is limited to Windows, Linux, Android, Raspberry Pi >> ant the like. He is experimenting with MacOS because I, his brother snd his >> sister are all Mac users.

    Please be aware that running macOS on anything other than Apple hardware breaks the SLA:

    <https://www.apple.com/legal/sla/docs/macOSTahoe.pdf>

    As discussed on the Support forums:

    <https://discussions.apple.com/thread/250646417?sortBy=rank>


    When I challenged 'Claude', my AI provider ....

    You didn't mention that running Apple software on non-Apple hardware is
    not in accordance with Apple's rules.

    =

    You're absolutely right - I should have mentioned that important point. Running macOS on non-Apple hardware (including VMware on Windows)
    violates Apple's Software License Agreement. Apple's EULA specifically restricts macOS to running only on Apple-branded hardware.

    This is a significant legal consideration that I overlooked in my
    response. While the technical solutions I provided might work, the
    entire setup your friend's son is attempting goes against Apple's
    licensing terms.

    I should have led with that disclaimer rather than jumping straight into troubleshooting. Thanks for the correction - it's an important
    distinction between what's technically possible and what's legally
    permitted according to the software license.

    =

    I replied ....

    Buck up! ChatGPT wouldn't have made that mistake!

    =

    You're probably right about that! It was a significant oversight on my
    part to dive straight into technical solutions without addressing the licensing issue first. That's exactly the kind of important context that should come before the "how to fix it" part.

    I appreciate you pointing it out - it's a good reminder that being
    thorough means considering not just the technical aspects but also the
    legal and ethical dimensions of what someone is trying to do.

    =
    --
    Kind regards,
    David
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From richard@richard@cogsci.ed.ac.uk (Richard Tobin) to uk.comp.sys.mac on Sat Sep 20 11:10:27 2025
    From Newsgroup: uk.comp.sys.mac

    In article <10alms9$103jt$1@dont-email.me>,
    John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade >is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword? It's possible that a virtual
    machine may not be implementing the modifier keys correctly.

    -- Richard
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Graeme Wall@rail@greywall.demon.co.uk to uk.comp.sys.mac on Sat Sep 20 13:05:31 2025
    From Newsgroup: uk.comp.sys.mac

    On 20/09/2025 12:10, Richard Tobin wrote:
    In article <10alms9$103jt$1@dont-email.me>,
    John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >> 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade
    is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword? It's possible that a virtual
    machine may not be implementing the modifier keys correctly.


    When I upgraded my Mac mini it wouldn't recognise the magic keyboard
    until I had plugged it into the computer. Similarly with the mouse
    though the latter had partial recognition in that the cursor moved and
    the occasional click was obeyed. Scrolling didn't work at all. Again,
    pairing it with the computer reactivated it.
    --
    Graeme Wall
    This account not read.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Sat Sep 20 13:51:49 2025
    From Newsgroup: uk.comp.sys.mac

    Richard Tobin <richard@cogsci.ed.ac.uk> wrote:
    In article <10alms9$103jt$1@dont-email.me>,
    John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade
    is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword? It's possible that a virtual
    machine may not be implementing the modifier keys correctly.

    Common problems are mixing up characters that different between US and UK keyboards, ie ~#|\-4-u"@ etc.

    Although if the keyboard has got itself into Japanese or Russian or
    something then even letters can be problematic :)

    A simple way to test your keyboard at login is to type into the 'username' field where you can see the characters, rather than the password field where you can't. I'm not sure what to do on a Mac that makes you select a user picture rather than type a username - is there a secret button somewhere you can use to let you enter a username, eg for network login?

    Theo
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From John Hill@watcombeman@yahoo.co.uk to uk.comp.sys.mac on Sat Sep 20 15:49:32 2025
    From Newsgroup: uk.comp.sys.mac

    On 20 Sep 2025 at 13:51:49 BST, "Theo" <theom+news@chiark.greenend.org.uk> wrote:

    <div id="editor" contenteditable="false">Richard Tobin <richard@cogsci.ed.ac.uk> wrote:
    In article <10alms9$103jt$1@dont-email.me>,
    John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >>> 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade
    is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword? It's possible that a virtual
    machine may not be implementing the modifier keys correctly.

    Common problems are mixing up characters that different between US and UK keyboards, ie ~#|\-4-u"@ etc.

    Although if the keyboard has got itself into Japanese or Russian or
    something then even letters can be problematic :)

    A simple way to test your keyboard at login is to type into the 'username' field where you can see the characters, rather than the password field where you can't. I'm not sure what to do on a Mac that makes you select a user picture rather than type a username - is there a secret button somewhere you can use to let you enter a username, eg for network login?

    Theo
    </div>
    <div class="footer" onclick="setCursorToBottom()"></div>

    Kelvin replied:

    My credentials are simply lowercase letters and numbers, so key modifiers should not have been an issue. I did also check that case was applied correctly.
    --
    An infinitely complex system can fail in an infinite number of ways.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From John Hill@watcombeman@yahoo.co.uk to uk.comp.sys.mac on Sat Sep 20 15:57:12 2025
    From Newsgroup: uk.comp.sys.mac

    On 20 Sep 2025 at 08:59:05 BST, "John Hill" <watcombeman@yahoo.co.uk> wrote:

    My eldest son is attempting to upgrade Sequoia running on VMware on Windows 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade is done, it knows his name, but does not accept his password.

    Any suggestions as to why this should happen? One was that he would have to turn FileVault off before upgrading, but when he checked, FileVault was already off so that was not the problem.

    His technical competence far exceeds mine (before he retired he was Mr Fixit for supercomputers) but is limited to Windows, Linux, Android, Raspberry Pi ant the like. He is experimenting with MacOS because I, his brother snd his sister are all Mac users.

    Old John.

    I passed all contributions to Kelvin, and he replied:

    Please thank them on my behalf for their input. It might also be worth mentioning that this is merely a technical exercise, rather than a long-term use case. Basically, to find out if it can be done.

    He also added, ro me but I think it's worth passng on,

    Today I am mostly playing radios, having received a brand new version of a hardware platform from China yesterday. Currently in bug detection mode. There are many!

    My thsnks also to you alll!

    Old John
    --
    An infinitely complex system can fail in an infinite number of ways.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@hugybear@gmx.net to uk.comp.sys.mac on Sat Sep 20 18:56:08 2025
    From Newsgroup: uk.comp.sys.mac

    Am 20.09.2025 um 14:05 schrieb Graeme Wall:
    On 20/09/2025 12:10, Richard Tobin wrote:
    In article <10alms9$103jt$1@dont-email.me>,
    John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >>> 11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade
    is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword? It's possible that a virtual
    machine may not be implementing the modifier keys correctly.


    When I upgraded my Mac mini it wouldn't recognise the magic keyboard
    until I had plugged it into the computer. Similarly with the mouse
    though the latter had partial recognition in that the cursor moved and
    the occasional click was obeyed. Scrolling didn't work at all. Again,
    pairing it with the computer reactivated it.

    Absolutely no such issues with my mini M2pro updating to 26. Everything
    worked as intended and usual from the first second. Magic Keyboard as
    well as the Magic Mouse.

    J||rg
    --
    "Roma locuta, causa finita" (Augustinus)
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Jason H@jason_hindle@yahoo.com to uk.comp.sys.mac on Sat Sep 20 19:26:33 2025
    From Newsgroup: uk.comp.sys.mac

    On 20/09/2025 12:10, richard@cogsci.ed.ac.uk wrote:
    In article <10alms9$103jt$1@dont-email.me>,
    John Hill <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on Windows >>11.

    There is no problem seeing snd running the upgrade to Tahoe. When the upgrade >>is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword? It's possible that a virtual
    machine may not be implementing the modifier keys correctly.

    -- Richard
    I've seen that with Virtualbox. Might be worth trying the password with
    Caps-Lock engaged.
    --
    --
    A PICKER OF UNCONSIDERED TRIFLES
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Graeme Wall@rail@greywall.demon.co.uk to uk.comp.sys.mac on Sun Sep 21 12:40:58 2025
    From Newsgroup: uk.comp.sys.mac

    On 20/09/2025 17:56, J||rg Lorenz wrote:
    Am 20.09.2025 um 14:05 schrieb Graeme Wall:
    On 20/09/2025 12:10, Richard Tobin wrote:
    In article <10alms9$103jt$1@dont-email.me>,
    John Hill-a <watcombeman@yahoo.co.uk> wrote:
    My eldest son is attempting to upgrade Sequoia running on VMware on
    Windows
    11.

    There is no problem seeing snd running the upgrade to Tahoe. When
    the upgrade
    is done, it knows his name, but does not accept his password.

    A remote chance, but is it certain that the keyboard is producing the
    correct characters for his passsword?-a It's possible that a virtual
    machine may not be implementing the modifier keys correctly.


    When I upgraded my Mac mini it wouldn't recognise the magic keyboard
    until I had plugged it into the computer. Similarly with the mouse
    though the latter had partial recognition in that the cursor moved and
    the occasional click was obeyed. Scrolling didn't work at all. Again,
    pairing it with the computer reactivated it.

    Absolutely no such issues with my mini M2pro updating to 26. Everything worked as intended and usual from the first second. Magic Keyboard as
    well as the Magic Mouse.



    Interesting, I wonder why it just affected me.
    --
    Graeme Wall
    This account not read.


    --- Synchronet 3.21a-Linux NewsLink 1.2