Lock/Unlock buttons start car

Yes, I have a Viper Remote/Start model 4105V on 2006 Subaru Forester, everything works great except if I press the lock or unlock button on the 4 button remote it starts the car. Both the lock and unlock work the lock system but it also starts the car at the same time. I have tried everything I can think of but nothing seems to fix the problem. Please any help would be appreciated.

Not a big viper guy, do not know if this is possible, but could someone have programmed both the lock and unlock as a remote start button? Do you have a different remote that works properly?

No, we don't have a different remote, we have tried to reset everything to factory to see if programming was an issue. We also verified with multiple remotes, same results.

Lock and unlock on the 4105 platform puts the system into timer mode. Do you have your owner's manual? This is from the owner's guide.

"Timer mode is activated when these buttons (lock+unlock)are pressed simultaneously.
When you activate timer mode the parking lights flash four times, after a
one second delay the engine starts. To turn the engine off, without exiting
timer mode press the *
The system remains in timer mode and will start every three hours for a
maximum of six starts unless cancelled by turning on the ignition, or by
activating any of the shutdown inputs to the system.
The parking lights flash four times indicating timer mode is exited"
.

Thanks for the reply, I do have the manual and I did read about this but that is not what's happening to my system. If I press the "Lock" button the car starts, if I press the "Unlock" button the car starts and if I press the "Start" button the car starts. I doesn't seem right... What I have done to get around it was set the pulse to two so for it to start the "Start" button has to be pressed two times and this made the "Lock" and "Unlock" not start the car when pressed.

If anyone has a better idea or what I might be doing wrong I am open to suggestions... thanks!!!

Sorry, I should have read your first post more carefully. Was the issue there since install or did it just start happening?

I believe it was there from install, we noticed it early on.