Yes, Footon is right. The problem was in the UPBV algorithm. It is extremely complex. Some times it takes me several days to decide if an indicator with particular parameters has to use UPBV or not. It is not surprising that no other software supports such concept. UPBV and the Ambiguous Bars are the core concepts and know-how used in FSB Pro.

The concrete reason for the above issue was that the program applied the UPBV shift on the original time frame instead of the indicators LTF. It happens because the program compares the Position open price with the indicator value. I have missed the fact that the position price is determined by the main time frame. The correct behaviour is to compare the Position price with the previous value of a LTF indicator if the indicator is used for opening and its Base price is not Bar Open.

I want to examine this case once more time before releasing an official version. I have to fix the digital signature issue also, but I cannot figure it out now.
The problem is that the older licenses are issued for the public key of the old FSB Pro digital certificate. Now I sign the program with a new certificate (forced by Microsoft) and the old License Codes cannot validate the new signature. The license service thinks that your program is hacked with a broken digital signature.