(2024-04-07, 18:51)DarrenHill Wrote: If you could try one again and gather the debug log (wiki) of the update it would be useful.
It looks like you may somehow be an edge case given the number of users who have already downloaded Omega (both RC and final) without issue, but if possible it's something that is worth investigation.

But without the logs, there isn't much we can do.

(2024-04-07, 23:54)Hitcher Wrote: Nightly builds are now v22.

(2024-04-08, 00:27)zacgates99 Wrote:

(2024-04-07, 18:51)DarrenHill Wrote: If you could try one again and gather the debug log (wiki) of the update it would be useful.
It looks like you may somehow be an edge case given the number of users who have already downloaded Omega (both RC and final) without issue, but if possible it's something that is worth investigation.

But without the logs, there isn't much we can do.

Problem found and work around.

I tried to install and run the new Kodi using the -p portable and discovered that windows 11 would not allow the new Kodi to run do to a memory access violation.   This got me to thinking and I did a couple of tests, and I discovered the problem that is occurring.

Under Windows 11, Windows 12, and Windows 11 Beta, the new Kodi 21, during the migration is creating a memory violation access out of bounds error.  When this violation occurs, it ends up damaging both databases and causing Kodi to hang.  To get around this problem, you must run the install program as administrator.  Then when you run Kodi 21 for the first time, you also must run it as administrator.  This prevents the memory violation from occurring and allowing the migration to be completed without damaging the databases.  Once the migration is completed, you can just simply run Kodi as normal.

Someone may want to go through the migration process and figure out what is the memory violation.  Since running as administrator fixes it, it is probably a nonstandard permission command somewhere.

(2024-04-07, 16:17)zacgates99 Wrote: Here is how to create the issues. 


--------Way #1------
On a windows PC (Windows 11) install nexus (20.5) and index at least 50 to 100 titles into movies and TV.  Close Kodi and go back into it.  Now set the skin to any skin other than the 3 that is in version 21.  Close Kodi and reopen again.  Start and stop a video. Close Kodi.

Now upgrade to version 21. Open Kodi and you'll get a message that the skin and other add-ons have been deactivated. After that screen is cleared and the migration starts is where it hangs.  If you go into the task manager, it shows that Kodi is using 0% of the CPU and is not responding.

(2024-04-08, 03:43)crawfish Wrote:

(2024-04-08, 00:27)zacgates99 Wrote:

(2024-04-07, 18:51)DarrenHill Wrote: If you could try one again and gather the debug log (wiki) of the update it would be useful.
It looks like you may somehow be an edge case given the number of users who have already downloaded Omega (both RC and final) without issue, but if possible it's something that is worth investigation.

But without the logs, there isn't much we can do.

Problem found and work around.

I tried to install and run the new Kodi using the -p portable and discovered that windows 11 would not allow the new Kodi to run do to a memory access violation.   This got me to thinking and I did a couple of tests, and I discovered the problem that is occurring.

Under Windows 11, Windows 12, and Windows 11 Beta, the new Kodi 21, during the migration is creating a memory violation access out of bounds error.  When this violation occurs, it ends up damaging both databases and causing Kodi to hang.  To get around this problem, you must run the install program as administrator.  Then when you run Kodi 21 for the first time, you also must run it as administrator.  This prevents the memory violation from occurring and allowing the migration to be completed without damaging the databases.  Once the migration is completed, you can just simply run Kodi as normal.

Someone may want to go through the migration process and figure out what is the memory violation.  Since running as administrator fixes it, it is probably a nonstandard permission command somewhere.

You've again ignored the request for the log. I'm sure what you've described is what you experienced, but I, and everyone else, didn't need to do anything out of the ordinary to install Kodi 21. You're expecting people to reverse engineer your unique setup based on the very incomplete information you've provided to solve a problem only you have. Ain't nobody got time for that.

(2024-04-08, 03:22)davorf Wrote:

(2024-04-07, 23:54)Hitcher Wrote: Nightly builds are now v22.

Hello!

I understand that now they are v22, but this was almost a month ago, before v21 was officially released.

Is there a way to install v21 release without uninstalling nightly, and losing library and all the customisations I've made in the process?

Best regards,
Davor

(2024-04-08, 03:49)zacgates99 Wrote:

(2024-04-08, 03:43)crawfish Wrote:

(2024-04-08, 00:27)zacgates99 Wrote: Problem found and work around.

I tried to install and run the new Kodi using the -p portable and discovered that windows 11 would not allow the new Kodi to run do to a memory access violation.   This got me to thinking and I did a couple of tests, and I discovered the problem that is occurring.

Under Windows 11, Windows 12, and Windows 11 Beta, the new Kodi 21, during the migration is creating a memory violation access out of bounds error.  When this violation occurs, it ends up damaging both databases and causing Kodi to hang.  To get around this problem, you must run the install program as administrator.  Then when you run Kodi 21 for the first time, you also must run it as administrator.  This prevents the memory violation from occurring and allowing the migration to be completed without damaging the databases.  Once the migration is completed, you can just simply run Kodi as normal.

Someone may want to go through the migration process and figure out what is the memory violation.  Since running as administrator fixes it, it is probably a nonstandard permission command somewhere.

You've again ignored the request for the log. I'm sure what you've described is what you experienced, but I, and everyone else, didn't need to do anything out of the ordinary to install Kodi 21. You're expecting people to reverse engineer your unique setup based on the very incomplete information you've provided to solve a problem only you have. Ain't nobody got time for that.

If you want to be rude. Be rude.  So don't expect help from me when people like you are down right RUDE!

(2024-04-08, 03:49)scott967 Wrote:

(2024-04-07, 16:17)zacgates99 Wrote: Here is how to create the issues. 


--------Way #1------
On a windows PC (Windows 11) install nexus (20.5) and index at least 50 to 100 titles into movies and TV.  Close Kodi and go back into it.  Now set the skin to any skin other than the 3 that is in version 21.  Close Kodi and reopen again.  Start and stop a video. Close Kodi.

Now upgrade to version 21. Open Kodi and you'll get a message that the skin and other add-ons have been deactivated. After that screen is cleared and the migration starts is where it hangs.  If you go into the task manager, it shows that Kodi is using 0% of the CPU and is not responding.

OK I tried to follow "way #1", but on Windows 10.  You don't indicate if you installed 20.5 Windows x64, x86, or UWP versions.  I assume x64 and that's what I did.  I then added a movie source and did a scan (assume that's what you mean by "index") and then a TV Show source and scan (assume that is what you mean by "TV" -- not live TV or recorded TV).  Closed and opened then Installed skin "Amber".  Closed and opened and played a movie in Amber.  Closed and installed Kodi 21 x64 using defaults during install.  Kodi started.

"Open Kodi and you'll get a message that the skin and other add-ons have been deactivated. After that screen is cleared and the migration starts is where it hangs."

No.  Didn't see this.  Migration started with the splash screen showing.  I did not see the message about amber until migration completed and Estuary skin loaded (this must be the case as you need a skin loaded in order to show a dialog window.


So I then installed Arctic Zepher reloaded from Kodi repo, allowed Kodi to switch skins and see this:



So, can't recreate.

scott s.
.

(2024-04-08, 04:05)crawfish Wrote:

(2024-04-08, 03:49)zacgates99 Wrote:

(2024-04-08, 03:43)crawfish Wrote: You've again ignored the request for the log. I'm sure what you've described is what you experienced, but I, and everyone else, didn't need to do anything out of the ordinary to install Kodi 21. You're expecting people to reverse engineer your unique setup based on the very incomplete information you've provided to solve a problem only you have. Ain't nobody got time for that.

If you want to be rude. Be rude.  So don't expect help from me when people like you are down right RUDE!

Every line of my post was written to help you. Thanks for confirming you're not a serious poster. It saves time.