Updated package not applies on RDS

Question

the situation:
1. updated package was published and enabled for AD global group. No issues. The app was updated on global refresh (1hour) or on logon as it should be
2. the same published package was enabled for RDSH.
The updated package folder does appear in PrData\Appv\PACAGE_ID with previous package ID folder
get-appvclientpackage shows just one package v.0001
get-appvclientpackage -all shows just both packages v.0001 and v.0002
(see below powershell output and screenshot)
Sure in this situation the updated package does not apply...
What could be done?
Thx.
PS C:\Windows\system32> get-appvclientpackage -all
PackageId            : 40807a65-0cea-4e40-bdcf-7f7cb4787bc5
VersionId            : ad2f6e12-b161-42fd-8c45-4b954fa0ba34
Name                 : my_app 5.4.0 v00
Version              : 0.0.0.2
Path                 :
\\00VAPPVPUB-01\Content\my_app 5.4 v.00 21 Jan
                       2015\my_app 5.4.0 v00_2.appv
IsPublishedToUser    : False
UserPending          : False
IsPublishedGlobally  : False
GlobalPending        : False
InUse                : False
InUseByCurrentUser   : False
PackageSize          : 289720664
PercentLoaded        : 100
IsLoading            : False
HasAssetIntelligence : True
PackageId            : 40807a65-0cea-4e40-bdcf-7f7cb4787bc5
VersionId            : 7cd93749-8ea9-4498-92a5-6142371e5d28
Name                 : my_app 5.4.0 v00
Version              : 0.0.0.1
Path                 :
\\00VAPPVPUB-01\Content\my_app 5.4.0 v.00 13 jan
                       2015\my_app 5.4.0 v00.appv
IsPublishedToUser    : False
UserPending          : False
IsPublishedGlobally  : True
GlobalPending        : False
InUse                : True
InUseByCurrentUser   : False
PackageSize          : 229408841
PercentLoaded        : 100
IsLoading            : False
HasAssetIntelligence : True
PS C:\Windows\system32> get-appvclientpackage
PackageId            : 40807a65-0cea-4e40-bdcf-7f7cb4787bc5
VersionId            : 7cd93749-8ea9-4498-92a5-6142371e5d28
Name                 : my_app 5.4.0 v00
Version              : 0.0.0.1
Path                 :
\\00VAPPVPUB-01\Content\my_app 5.4.0 v.00 13 jan
                       2015\my_app 5.4.0 v00.appv
IsPublishedToUser    : False
UserPending          : False
IsPublishedGlobally  : True
GlobalPending        : False
InUse                : True
InUseByCurrentUser   : False
PackageSize          : 229408841
PercentLoaded        : 100
IsLoading            : False
HasAssetIntelligence : True
PS C:\Windows\system32>
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Answer 1

PackageId            : 40807a65-0cea-4e40-bdcf-7f7cb4787bc5
VersionId            : 7cd93749-8ea9-4498-92a5-6142371e5d28
Name                 : my_app 5.4.0 v00
Version              : 0.0.0.1
Path                 :
\\00VAPPVPUB-01\Content\my_app 5.4.0 v.00 13 jan
                       2015\my_app 5.4.0 v00.appv
IsPublishedToUser    : False
UserPending          : False
IsPublishedGlobally  : True
GlobalPending        : False
InUse                : True
InUseByCurrentUser   : False
It can't apply version 0.0.0.2 because 0.0.0.1 is in use (InUse = TRUE). If you don't have the app open then it may be still locking a file. Check that there are no other users logged into that machine and check to see if there are any executables related to
"my_app 5.4.0 v00" that are running.