LOR 4.3.28 crashes after install

[Trailrider 0]

Anyone else having problems installing the latest upgrade 4.3.28? Tried to upgrade got all kinds of error messages. Uninstalled program, redownloaded file, reinstalled and still received error messages. Rolled back to previous ver. 4.3.26 and everything seems fine. May just be me but it's strange a previous version works fine.

Edited June 15, 2018 by Trailrider

[caniac 388]

has issues with msi libraries.

[tomsusie 29]

I had a problem in that it would not finish installing.  Stopped and restarted install and selected repair.  Program installed completely after that.    Have not used it yet but all seems to be working -- program shows latest update as being active.

[caniac 388]

7 minutes ago, tomsusie said:

I had a problem in that it would not finish installing.  Stopped and restarted install and selected repair.  Program installed completely after that.    Have not used it yet but all seems to be working -- program shows latest update as being active.

did the same and all is working, I had a pending update holding everything up.  Thank you MicroSlouch.

[GriswoldStyle 105]

Good thing I didn't update mine last night. I'm going to wait a couple days till everybody says it installed properly. Just to be on the safe side.

[caniac 388]

3 minutes ago, GriswoldStyle said:

Good thing I didn't update mine last night. I'm going to wait a couple days till everybody says it installed properly. Just to be on the safe side.

check and make sure you don't have a Microsoft update pending first, once that installed and my PC rebooted everything played nice.

[ItsMeBobO 436]

I too had many issues with this install but I was able to eventually install it.  

1)  Avast claimed it was potential virus.   Would not allow me to mark as safe and claimed to send it for examination.  

2) Later file was deemed safe and install seemed to work BUT

3) When I attempted to load control panel the install started again but said it could not find MSI in a temp location.   This went on for a while while I tried to find the msi by searching and failed.

4) I did not DL install.exe again.   Instead I just ran the install again from its downloaded location and it worked.

5) Post did not recall my files folder and made me navigate to it.  

 

[TheDucks 203]

I had to reboot, then still needed to run a Repair Install   W10 x64

[default 180]

43 minutes ago, ItsMeBobO said:

1)  Avast claimed it was potential virus.   Would not allow me to mark as safe and claimed to send it for examination. 

Remember, DevMike posted about this.

Just in case others may have missed his post.

Alan...

Edited June 15, 2018 by default

[DevMike 429]

Does sound like there are 2 things going on here.

1 - is definitely that MS update.  I had several of them come through in the last few days including on our build machine and the installer test machine.  I like W10 a lot more than I ever liked W8, but this "update when WE say so" (MS) is starting to give us heartburn.

2 - The other is most likely the new code for Dynamic files.  AV programs can be jerks about false positives, which was one of the reasons why we have spent a few thousand dollars on digital signing certificates for our programs (find one of our EXE's and then right click on it.  Check the Digital Signature tab, and you'll see our certificate).  Having a certificate, issued by a trusted authority which ours is, is supposed to tell the AV program to back off a little bit.  They don't.

I did test the installer (we test ALL installers) and didn't have any issues - but I did have all the updates installed.  I think Windows Firewall did warn me about HWU wanting to go out on the net, and I just let it through.

If you do have an AV program that won't cooperate, please let us know what it is.  We will try to contact them, but in the end you will probably need to talk to them.  When we do we never hear from them or worse:  they want us to buy their p roduct just to have access to their help desk and THEN they don't get back to us.

[DevMike 429]

Of course, with all that said, a 4.3.30 is already being built by me.  Apparently there is a bug in SuperStar that needs to be addressed.  Keep on eye out.

[PhilMassey 301]

Just for reference, my install appeared to complete, but upon starting up SE reported that Users\appdata\local\temp\ verylongfilename..msi could not be found. Rebooted, same thing. 

Uninstalled, and ran the 4.3.18 Regwipe and reinstalled from the same download and the normal behavior resumed Lorpost ran and all seems good now.

W10 64 bit, No AV other than Win Defender.

[PhilMassey 301]

4.3.30 installed on top of 4.3.28 with zero issues. Took 2 minutes,  everything seems to be working normally.

[caniac 388]

11 minutes ago, PhilMassey said:

4.3.30 installed on top of 4.3.28 with zero issues. Took 2 minutes,  everything seems to be working normally.

ditto

[Brad Stucky 2]

Might this change in S4 have something to do with the installation problem I had on 2 different computers?  Installing 4.3.30 over 4.3.26 on Windows 7-64 pro,  I received an error that the program could not locate a resource file in a temp directory somehware.  (lightorama.msi I believe)  Sorry I didn't get any screen  captures.   The program got into some kind of loop so I had to task manager abort the process.   I then tried a re-install and selected a repair of the installation and everything seemed fine after that.   This same event happened on 2 different computers.

Edited June 16, 2018 by Brad Stucky
mistake in version number

[Tharkun 4]

i keep getting same error, have tried reloading and downloading and starting over three times now. Running WIN7 on hybrid drive Sonly Viao laptop.  trying to to new install of S4 V4.3.30

[Tharkun 4]

Went back to version 4.3.26 and was able to install on laptop.  No install errors and no issues.

[Trickyd 9]

Hello

 

also got the same error, did second try with repair option, now works on three  machines, even on a virtual machine on a mac.

 

strange behaviour though.

 

best regards

 

Dick de Wit

The Netherlands

[Denny 42]

I also have the same problem.  Tried updating two machines from 4.0.38 today and get the same error message.  Rolled back to 4.0.38.

 

Edited June 22, 2018 by Denny
spelling correction

[DevMike 429]

it is looking more and more like Microsoft has changed the rules on us again.  We just don't know what the changes are yet or if we can even get around them.  We have not been able to duplicate the issue, which makes tracking it down much harder.   We will keep looking.

FYI:  I am reasonably sure this has nothing to do with the new dynamic files, but has something to do with how uninstall information is kept in the registry - something that Windows itself controls.  That's just speculation at the moment however.

It is possible that I did not create the installer correctly, but if that were the case I would expect us to be able to immediately duplicate the issue.

--------

If you are having an issue, please UNINSTALL your old version first, then install the new version.  Let us know if that helps or not.

If it still did not help, uninstall, then do a registry wipe and re-install.  Does that help?

If you do get the error, please take a screen shot of it for us.  It's hard to do any research without the exact error message and title.

I'd like to see what is happening for myself.  If you happen to get the error, and if you can/have the time, don't go any further and open a help desk ticket.  I'll set up a remote session so I can get a first hand look at what is happening.

[Denny 42]

These are the messages I receive when I try to update.

 

[Denny 42]

Uninstalled the old version and tried to install again, no luck.  Installed LOR 5 beta with no problems.  Uninstalled it and tried to install .30 again with no luck.  Installed the 4.3.018 with no problems, which is what I am using now.  Same problem on my Vaio laptop as on the Dell desktop.  Both are running Windows 10 64 bit. 

Show machine is Windows 7, but really don't want to mess with it unless I am sure it will load without problems. 

[dibblejr 987]

Sounds like one of my issues last year. My windows 10 computers (3 of them) would not play well with anything above 4.3.18 which is why I am stuck and happily running .18

All were the free Win10 upgrade.

Purchased a brand new top of the line Alienware laptop to run the show and never attempted to run anything but .18 on it.

IMO- don’t upgrade that win 7 machine. Once you do you are stuck with Win10, that was where I screwed up.

JR

Edited June 25, 2018 by dibblejr

[DevMike 429]

Denny:

Thanks!  Those messages tell me there is a permissions issue, probably not of your own making.  What is interesting is that you are at the point of installing Direct X, since I can see the direct X setup window.  This could be a big clue - MS may have changed the way it is uninstalling/reinstalling DirectX and flubbed it.  I don't remember touching anything in the installer for Direct X, but I will double check that on my end.  The fact that you are on the DirectX installer also tells me that the installer has nearly completed all it's functions.  The last 2 things it should be doing are installing Direct X, and then setting some registry values.  This is probably why doing a 'repair' installation is working.

-------

First, ensure you have done a COLD restart.  This is going to sound wrong, but trust me on this:  Press the Windows 10 start button, select the power icon, then select RESTART.  Don't select Shut down.  It is completely opposite of how it's on the start menu:  Restart is a COLD start, where Shut Down is a WARM restart - even if it looks like the power is OFF to the computer.

Try this procedure and let me know if it works or not:

1 - Go to the software download page and RIGHT click the link to download

2 - Select 'Save Link As'  (IE:  'Save Target As')

3 - You'll be asked to place the file on your computer.  Tell it to put it on your DESKTOP

4 - Allow the download to complete.

5 - Left click ONCE on the LOR-4.3.30.exe file that is now on your desktop somewhere (to highlight it).  Then right click.

6 - Select 'Run as Administrator'

7- Allow the install to finish (or hit that error again).

If you do hit that error again close up all those messages.

1 - Goto Add or Remove programs in Windows 10

2 - Select Light O Rama and hit uninstall

3 - You should get another box that pops up saying do you want to install, uninstall or repair.  Select REPAIR

4 - Allow that to finish (or get the error message)

 

[Denny 42]

1 hour ago, DevMike said:

Denny:

Thanks!  Those messages tell me there is a permissions issue, probably not of your own making.  What is interesting is that you are at the point of installing Direct X, since I can see the direct X setup window.  This could be a big clue - MS may have changed the way it is uninstalling/reinstalling DirectX and flubbed it.  I don't remember touching anything in the installer for Direct X, but I will double check that on my end.  The fact that you are on the DirectX installer also tells me that the installer has nearly completed all it's functions.  The last 2 things it should be doing are installing Direct X, and then setting some registry values.  This is probably why doing a 'repair' installation is working.

-------

First, ensure you have done a COLD restart.  This is going to sound wrong, but trust me on this:  Press the Windows 10 start button, select the power icon, then select RESTART.  Don't select Shut down.  It is completely opposite of how it's on the start menu:  Restart is a COLD start, where Shut Down is a WARM restart - even if it looks like the power is OFF to the computer.

Try this procedure and let me know if it works or not:

1 - Go to the software download page and RIGHT click the link to download

2 - Select 'Save Link As'  (IE:  'Save Target As')

3 - You'll be asked to place the file on your computer.  Tell it to put it on your DESKTOP

4 - Allow the download to complete.

5 - Left click ONCE on the LOR-4.3.30.exe file that is now on your desktop somewhere (to highlight it).  Then right click.

6 - Select 'Run as Administrator'

7- Allow the install to finish (or hit that error again).

If you do hit that error again close up all those messages.

1 - Goto Add or Remove programs in Windows 10

2 - Select Light O Rama and hit uninstall

3 - You should get another box that pops up saying do you want to install, uninstall or repair.  Select REPAIR

4 - Allow that to finish (or get the error message)

 

Mike, 

That worked when I did the "Repair" step.  I was able to open the Sequence Editor without problems after REPAIR.  Sequence Editor now shows version 4.30 and seems to work as normal.  Thanks a lot.

In case it helps though, these are the error messages I received BEFORE the "Repair" steps.