Thanks for all the helpful replies. I slightly feared messing it up so tried Apple chat and ended up with a call in 2mins.
Chap from US (amazing!) was really helpful and whilst unsure, in 20mins reviewed through screenshare and ascertained that I needed to do a special boot to a mode that enabled me to choose to upgrade encryption security of the hard disk to Full. All done. Wallet happy. Thanks again for all so kindly making time to offer such comprehensive replies too. On Friday, 28 March 2025 at 11:16:56 UTC Cliff Wootton wrote: > Jason's suggestions are good. Follow up with these if you need them. > > --- > > Maybe a disk repair with Disk Utility might help to start with if you > haven't already done it. > > --- > > There might be some evidence in a log file somewhere that will give you a > clue. A lot of apps send their logs to something called SYSLOG which > aggregates them into one big list while others log into their own private > log files. > > HD -> Library -> Apple -> Logs > > Home folder -> Library -> Logs > > The Console app in the Applications -> Utilities folder is useful for > inspecting them without going to the Terminal app > > --- > > From the Terminal app, look in: > > */var/log* > */var/logs* > > *ls -la /var/log* > > Will show you the permissions and owners. > > Historical logs are rotated and zipped to save space on a regular basis if > you want to look further back in the past. > > --- > > Look for wallet related files. Spotlight might not find what you want, nor > will the Finder's find command (which is based on Spotlight). Use the > command line *find* command from the Terminal app to locate any files > that have 'wallet' in their name. This will find files anywhere in the > entire system that Spotlight won't. The prefixing 'i' on the find by name > modifier tells it to ignore case. Use *-name* for case sensitive searches: > > *find / -iname "*wallet*" -type f* > > However, it's hard to recommend what to do with the files you find, but at > least you will have a list to talk to the Apple support teams about. > > Hope this helps > > Cliff > > > > On Friday, 28 March 2025 at 10:30:21 UTC Jason Davies wrote: > >> I think it's the whole device that is refusing? >> >> Adam, I suspect this is that macOS has detected an unlocked door >> somewhere and hit an alarm. That means it's hard to know exactly what it >> might be. They do seem to say to contact them if this stuff doesn't work >> which strengthens my suspicion it's going to be very specific. So you might >> need to do some diagnostics: I'd first try to identify whether it's user, >> OS or hardware-based. >> >> - >> >> create a new user and see if that user is allowed to do it (ie pin >> down whether it's a user issue or underlying OS issue) >> - >> >> if you can boot it from USB from a clone (this worked ok for Intel, I >> believe, harder for Silicon), install the OS to that and startup with a >> virgin system and try to add the card: that will let you see if it's >> hardware related. If you succeed, you might need to deactivate it >> afterwards as they have limits on how many devices they can be linked to. >> >> At that point it's a question of either working out where the specific >> alarm is coming from (something you installed?) and removing it, or nuking >> and building up (eg seeing if erasing then reinstalling from TM will work), >> but at least you know which 'domain' it is in. >> >> I didn't post all this as I hoped someone expert would lean over and say >> 'ah it's probably this' and flick a switch, which might still happen;) >> >> cheers, >> >> Jason >> >> On 28 Mar 2025, at 9:32, Paul Russell wrote: >> >> I don’t think you can edit existing cards in the wallet, however you >> shouldn’t normally need to do this, as even when you get a new card with a >> new expiry date etc it just automagically updates in the wallet without >> intervention. >> >> If you’re having problems with an existing card in the wallet though then >> maybe try removing it and adding it again? >> >> On 27 Mar 2025, at 13:43, Adam Pymble <[email protected]> wrote: >> >> Hello all >> >> I want to edit card details on the above. >> >> I have a warning as attached. >> >> But when I click Learn More I'm directed to perhaps the most unhelpful >> Apple page ever, as it doesn't tell me what to do (Intel MBPro, 13" on >> latest macOS) >> >> https://support.apple.com/en-gb/118268 >> >> Any ideas please?! >> >> "It just works....' >> >> ;) >> -- >> You received this message because you are subscribed to the Google Groups >> "Sussex Mac User Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion, visit >> https://groups.google.com/d/msgid/smug/bd4c491e-8026-4f79-9f0f-55e2632dfe23n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/smug/bd4c491e-8026-4f79-9f0f-55e2632dfe23n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> <Screenshot 2025-03-27 at 13.41.14.png> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Sussex Mac User Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> >> To view this discussion, visit >> https://groups.google.com/d/msgid/smug/E15C2E13-4191-4E1D-8DAE-9089103608F4%40sonic.net >> >> <https://groups.google.com/d/msgid/smug/E15C2E13-4191-4E1D-8DAE-9089103608F4%40sonic.net?utm_medium=email&utm_source=footer> >> . >> >> Cheers, >> >> Jason >> > -- You received this message because you are subscribed to the Google Groups "Sussex Mac User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion, visit https://groups.google.com/d/msgid/smug/9539f3bd-0b55-4d1d-8690-a997e18d9520n%40googlegroups.com.
