Author Topic: Hot fix install locks SE (v23.0.1.0 64-bit) (Resolved, User error)  (Read 230 times)

byates

  • Senior Community Member
  • Posts: 103
  • Hero Points: 8
I've just updated to the latest build ((v23.0.1.0 64-bit) with a fresh install. I did not let the installer pull in any previous version's information (renamed the old config directory). I then attempted to install the latest hot-fix (hotfix_se2300_3_cumulative). SE locks at that point using 100% of a single CPU core.  After several minutes I killed the application, deleted the config directory, and tried again.  Same result.

SlickEdit Pro 2018 (v23.0.1.0 64-bit)
Build Date: February 14, 2019
Emulation: CUA
OS: Windows 10 x64
OS Version: 10.00.0 
Memory: 10% Load, 6994MB/65465MB Physical, 9368MB/75193MB Page File, 4505MB/134217727MB Virtual
Shell Information: C:\WINDOWS\system32\cmd.exe /q
Screen Size: 3691 x 2160, 3840 x 2160
Installation Directory: C:\Program Files\SlickEdit Pro 23.0.1\ (non-removable drive,NTFS,453962MB free)
Configuration Directory: C:\Users\brent\Documents\My SlickEdit Config\23.0.1\ (non-removable drive,NTFS,453962MB free)
« Last Edit: February 15, 2019, 08:00:42 pm by byates »

SlickEdit Support

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 278
  • Hero Points: 25
Re: Hot fix install locks SE (v23.0.1.0 64-bit)
« Reply #1 on: February 15, 2019, 07:52:17 pm »
That hotfix you're trying to load is for 23.0.0.*

It won't load in v23.0.1...although it should handle that more gracefully than a lock-up.

v23.0.1 has all the hotfixes from the 23.0.0.* hotfix rolled into it.

We'll look into this.

Thanks,
SlickEdit Support

byates

  • Senior Community Member
  • Posts: 103
  • Hero Points: 8
Re: Hot fix install locks SE (v23.0.1.0 64-bit)
« Reply #2 on: February 15, 2019, 07:54:57 pm »
 :o

Should have caught that. Thanks!

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1025
  • Hero Points: 86
Re: Hot fix install locks SE (v23.0.1.0 64-bit) (Resolved, User error)
« Reply #3 on: February 21, 2019, 02:18:17 pm »
This is fixed from 23.0.1.1 on.  There was a bug in the code that handled the case where the versions don't match that made it hang.  Thanks for the report.