Possible bug in the installer / skin installer?
Posted: December 19th, 2018, 5:08 am
Rainmeter 4.3.0.3266 beta (64-bit)
Language: English (1033)
Build time: 2018-11-30 16:52:14
Commit Hash: 8ff9f826
Windows 10 Enterprise 1803 64-bit (build 17134) - Romanian (1048)
Path: C:\Program Files\Rainmeter\
SkinPath: C:\Users\Zedd\Documents\Rainmeter\Skins\
SettingsPath: C:\Users\Zedd\AppData\Roaming\Rainmeter\
IniFile: C:\Users\Zedd\AppData\Roaming\Rainmeter\Rainmeter.ini
AMD Radeon HD 7500/7600 Series
After installing Rainmeter using the defaults and restarting the system, the application doesn't start with Windows, despite it being present and enabled in the Task Manager / Startup tab. Not only that, but after creating the above .rmskin, uninstalling and reinstalling Rainmeter (to again test if it starts up with Windows) and finally installing using the defaults the said .rmskin package, the application doesn't automatically load the selected layout from the included ones, despite everything being checked to do so.
Basically I have to both manually start Rainmeter and manually load the desired layout after installing the .rmskin. This did not happen in version 3260 beta (64-bit), in a similar scenario (e.g. version 1.2.0 of my .rmskin). I've even tried running everything (Rainmeter's installer, Rainmeter application and the skin installer) as administrator (I'm already on an adminstrator account, UAC disabled, etc.), but it didn't change anything. With the previous version (3260b) I only needed to run Rainmeter as an adminstrator, and that was only because I had some registry queries in one of my skins.
Since we're at it, if at some point in the future things need administrator privileges to be correctly run, please write that somewhere on the site / forum. In the meantime, I hope you can reproduce the issue, so that you can fix it (if it needs to).
EDIT: Ok, I narrowed down the issue a little bit, and my skin is fine, it's not the culprit. I've installed and tested Rainmeter 4.2 Final Release - r3111 using my skin and it has the same problem as 4.3.0.3266 beta! Although I deleted v. 4.3.0.3260 beta from my internal drive after downloading v. 4.3.0.3266, I fortunately had a copy of it on my external drive. Guess what: when I again installed the 4.3.0.3260 beta and my skin, it all worked flawlessly! So there's something wrong in both 4.2.0.3111 and 4.3.0.3266b, but not in 4.3.0.3260b, because the latter starts with Windows and loads the skin layout just fine. Suggestion: keep a couple of older versions of Rainmeter available for download for a while, because in similar situations, there aren't much options to roll back to a previous beta.
Language: English (1033)
Build time: 2018-11-30 16:52:14
Commit Hash: 8ff9f826
Windows 10 Enterprise 1803 64-bit (build 17134) - Romanian (1048)
Path: C:\Program Files\Rainmeter\
SkinPath: C:\Users\Zedd\Documents\Rainmeter\Skins\
SettingsPath: C:\Users\Zedd\AppData\Roaming\Rainmeter\
IniFile: C:\Users\Zedd\AppData\Roaming\Rainmeter\Rainmeter.ini
AMD Radeon HD 7500/7600 Series
After installing Rainmeter using the defaults and restarting the system, the application doesn't start with Windows, despite it being present and enabled in the Task Manager / Startup tab. Not only that, but after creating the above .rmskin, uninstalling and reinstalling Rainmeter (to again test if it starts up with Windows) and finally installing using the defaults the said .rmskin package, the application doesn't automatically load the selected layout from the included ones, despite everything being checked to do so.
Basically I have to both manually start Rainmeter and manually load the desired layout after installing the .rmskin. This did not happen in version 3260 beta (64-bit), in a similar scenario (e.g. version 1.2.0 of my .rmskin). I've even tried running everything (Rainmeter's installer, Rainmeter application and the skin installer) as administrator (I'm already on an adminstrator account, UAC disabled, etc.), but it didn't change anything. With the previous version (3260b) I only needed to run Rainmeter as an adminstrator, and that was only because I had some registry queries in one of my skins.
Since we're at it, if at some point in the future things need administrator privileges to be correctly run, please write that somewhere on the site / forum. In the meantime, I hope you can reproduce the issue, so that you can fix it (if it needs to).
EDIT: Ok, I narrowed down the issue a little bit, and my skin is fine, it's not the culprit. I've installed and tested Rainmeter 4.2 Final Release - r3111 using my skin and it has the same problem as 4.3.0.3266 beta! Although I deleted v. 4.3.0.3260 beta from my internal drive after downloading v. 4.3.0.3266, I fortunately had a copy of it on my external drive. Guess what: when I again installed the 4.3.0.3260 beta and my skin, it all worked flawlessly! So there's something wrong in both 4.2.0.3111 and 4.3.0.3266b, but not in 4.3.0.3260b, because the latter starts with Windows and loads the skin layout just fine. Suggestion: keep a couple of older versions of Rainmeter available for download for a while, because in similar situations, there aren't much options to roll back to a previous beta.