Error installing 26.0.2

Hi MTarr ,

MTarr said:

I installed 26.0.2 as admin and that worked. I then installed 26.1.1 as user but it did not work, so I installed it as admin and that worked.

Pretty sure there is a permission thing going on here. Windows file permissions can get convoluted very quickly. Since you may be doing this on a number of machines, and you want a repeatable process, I would suggest starting over using the install for LTspice 26.1.1, and using the "Install on Server" option. This is set up to allow admins to install on individual machines that others will use. In your case, you are both the admin and the user.

To do so,

1. log in as Admin and remove all versions of LTspice. 
2. Run the Install for LTspice 26.1.1, but without using the command line.
3. Choose "Server"
4. When finished, log out as Admin
5. Log in as yourself
6. Run LTspice. LTspice will set up it's files for your user name, not Admin.
7. Now, you should be able to update normally.

In general, once an Admin has "touched" some files, they will get locked up for users. You may not even know what files have been modified, as you didn't directly open or edit.

If this method works for you, it should apply to other user PCs on which you are installing LTspice. LTspice is a bit odd in Enterprise environments, in that it doesn't play that well with Enterprise software management systems. This is a tradeoff; enabling easy installation of a complete design environment without sending users off to get libraries, etc.

mike

Hi MTarr ,

MTarr said:

I installed 26.0.2 as admin and that worked. I then installed 26.1.1 as user but it did not work, so I installed it as admin and that worked.

Pretty sure there is a permission thing going on here. Windows file permissions can get convoluted very quickly. Since you may be doing this on a number of machines, and you want a repeatable process, I would suggest starting over using the install for LTspice 26.1.1, and using the "Install on Server" option. This is set up to allow admins to install on individual machines that others will use. In your case, you are both the admin and the user.

To do so,

1. log in as Admin and remove all versions of LTspice. 
2. Run the Install for LTspice 26.1.1, but without using the command line.
3. Choose "Server"
4. When finished, log out as Admin
5. Log in as yourself
6. Run LTspice. LTspice will set up it's files for your user name, not Admin.
7. Now, you should be able to update normally.

In general, once an Admin has "touched" some files, they will get locked up for users. You may not even know what files have been modified, as you didn't directly open or edit.

If this method works for you, it should apply to other user PCs on which you are installing LTspice. LTspice is a bit odd in Enterprise environments, in that it doesn't play that well with Enterprise software management systems. This is a tradeoff; enabling easy installation of a complete design environment without sending users off to get libraries, etc.

mike

Hi Mike,

Thank your for all your help. I will try you suggestion above.

At first I was surprised that more folks didn't have this issue. The I was surprised that other Win 11 PC's, all up to date, behaved differently when applying the same update.

The mysterious ways the windows OS works!

Best regards,

Morty

MTarr said:

The mysterious ways the windows OS works!

So true. We all must remember that Windows has long been a house of cards built on a house of cards. 

mike