musoware forums

By jove you've done it!
All three PC'e are now upgraded to V2.5.27.3, and all retained the license, with logging still enabled.

Thank you Jeremy.

OK - well both of them were upgraded from V2.5.25.3, so I'll need to wait for another update on all 3 PC's to test this.

Jeremy, I decided to try this on the remaining 2 PC's I have muso installed on.
Both are now at V2.5.27.2 but in each case the license was lost and I needed to reactivate logging.
So from my experience the issue is not fixed yet.

I was about to say YES to the update, then remembered I hadn't turned on logging after the last update. So I said SKIP, then ran Muso and enabled logging. I thought muso would offer the update after a restart. But I think now, that SKIP means to skip this update altogether. So looks like I can't ver...

Jeremy, I have just updated to V2.5.27.1 - I needed to reapply the license, as you explained.
I will await the next update to check if the problem is resolved.

Jeremy, thanks for this. I will await your fix.
Regards, Rob

Have now updated to V2.5.25.4 - I have turned on diagnostic logging and reapplied the license.
I have emailed the log file to you.

On a second PC I allowed muso to update, with the same result.
After the update logging had been disabled, the Machine ID was retained, but the license was blank.
I reactivated logging, and have emailed the log file to you.

I just realised that some of the log got lost when copying. Here is the complete log ... +----+--------------+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------- | Th | Timestamp | Timing |...

Well I am for now just trying this on one PC. The automatic update went OK, except after the update, it is still on Build 2.5.25.3. And diagnostics logging has been turned off? Anyway I checked the license - the Machine ID was retained, but the license field is blank. So I re-entered the license and...