Note: This issue has been resolved in Framework 2.5.9 update