Replies

I’ve found this site to be quite civilised compared to some forums I’ve been on. I won’t go into too much detail as it’s off-topic for here but I found members of a particular Irish forum to be quite aggressive at times.

I agree with OscarCP that people can be a bit cranky here but I think a lot of that is frustration with where the IT world is going, especially Microsoft. So I totally get it because that has been me at times too.

4 users thanked author for this post.

Mr. Austin, Cybertooth, Charlie, OscarCP

On more recent versions you can also right-click the tray icon to disable autostart if not logged in. But there’s plenty more that I don’t like about it too. Such as the inability to install it as a system-wide application, so each user has their own instance of it. It’s also very bloated.

I’m in Ireland and occasionally some sites think my Vodafone connection is in the US because they got a block of IPs that was previously from there. I’ve also seen Virgin Media connections using IPs formerly allocated to Austria and Poland. It can take a long time for databases to update; in the case of Virgin Media it was over a year.

1 user thanked author for this post.

satrow

They really are doing everything they can to push me away from Windows 11. Am I going to need a throwaway MS account in work to deploy Pro machines now?

anonymous wrote:

Can someone please post a fully-working PS script that doesn’t result in:

Test-Path : Cannot bind argument to parameter 'Path' because it is an empty string.
At line:3 char:21
+        if(Test-Path $path){
+                     ~~~~~
    + CategoryInfo          : InvalidData: (:) [Test-Path], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.TestPathCommand

Many thanks.

It doesn’t seem to like when the PATH variable ends with a semicolon.

Sounds to me like they want more involuntary beta testers.

1 user thanked author for this post.

Cybertooth

anonymous wrote:

Change the CR2032 battery for a fresh one.  Most users of Z420 seem to be using ECC or registered ECC ram, are you?

This! The Xeon E5 CPU needs registered memory. It would have a part number such as PC3-12800R on the module. The R is important, U or E will not work.

I use my laptop on mains power most of the time but it has a “Maximise my battery health” option in the UEFI that prevents it charging above 80%. It does me fine because I still have a usable battery life when I do need it, but it won’t wear out from being at 100% the majority of the time.

Desktops do have batteries but anything made in the last 25 years usually has just a small coin-cell that isn’t susceptible to this type of failure.

It would only work for a new user account but it wouldn’t matter if it was a new account when Windows was first installed, or a new user account created later.

I’ve never tried to change the name of the user profile folder after the account was created. I always considered that to be a no-no because any amount of items could be tied to the original name.

Just giving a quick update on this. It’s not resolved but I found that if I log out first and then shut down, it never happens.

I mentioned this before but no harm saying it again. A workaround I’ve often used is to create a local account first and then to convert it to a Microsoft account later in Settings.

If you don’t feel like meddling with the registry, Microsoft have an easy fix MSI file that does this for you.

https://download.microsoft.com/download/0/6/5/0658B1A7-6D2E-474F-BC2C-D69E5B9E9A68/MicrosoftEasyFix51044.msi

Thanks for that. I did find it before in a Google search but dismissed it because I don’t use ProtonVPN. But I was able to enable the shutdown logging to see what might be happening. Looks to be some KDE processes:

[ 1685.912062] systemd[1]: systemd-journald.service: Got notification message from PID 438 (FDSTORE=1)
[ 1685.912076] systemd[1]: systemd-journald.service: Added fd 24 (n/a) to fd store.
[ 1726.720678] systemd[1]: systemd-resolved.service: Got notification message from PID 825 (WATCHDOG=1)
[ 1742.225382] systemd[1]: systemd-timesyncd.service: Got notification message from PID 826 (WATCHDOG=1)
[ 1752.975408] systemd[1]: session-3.scope: Stopping timed out. Killing.
[ 1752.975461] systemd[1]: session-3.scope: Killing process 1543 (kded5) with signal SIGKILL.
[ 1752.975488] systemd[1]: session-3.scope: Killing process 8146 (kded5) with signal SIGKILL.
[ 1752.975506] systemd[1]: session-3.scope: Killing process 8147 (drkonqi) with signal SIGKILL.
[ 1752.975869] systemd[1]: session-3.scope: Failed with result ‘timeout’.
[ 1752.975874] systemd[1]: session-3.scope changed stop-sigterm -> failed

I’m experimenting with Audacious at the moment.