Comments
-
Thank you for the reply. I do have a case on this already. Here is the case number: Case #:02181100 We cloned our WHD server and ran the update on that. With this, I was able to show the settings of our production 2026.1 against our test 2026.2.1. Both these servers are still available if more data collection is needed.…
-
That one is fine. It still uses all the same under the hood programing unlike 2026.2.X The biggest noticeable change is SW changing their version number layout. If this is a VM, I would take a snapshot, or if it is a physical server with RAID 1, pull a drive for a quick fallback. But you shouldn't need to… But always be…
-
I guess we can just call this release 2026 disaster number 2 I already have a support ticket open on the follow but want to share this with the community. Also this update should be pulled…again. The only reason I can think of that they are not pulling it is because we are live testing and providing them data to fix this…
-
This 8443 thing seems to be our wall. I opened a ticket with Support and he started to troubleshoot with me. He was going to ask me to do something and then suddenly stopped. Then said, he just found an internal document about the update overwriting existing files and then said they are recommended I don't upgrade. I also…
