Question
Ascension Health
US
Last activity: 1 May 2018 7:47 EDT
Windows 10 upgraded and my Native Control Name Match Rule quit working?
On April 3 I was working on a project with Native Control Match rules and everything was running smoothly. This project is over 6 months old and has been running consistently. On April 4 I restarted my machine after a windows update [(2018-03 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4088782)] and all my Native Control matches quit working? Several other projects using different match rules had no issues.
This happened the day before to my teammate and he refreshed his cache to fix it. I refreshed the project cache's, TFS cache and Visual Studio cache and nothing brought them back. Rebooted and pulled a new package from TFS multiple times. Still nothing. Finally gave up for the day and was going to do a complete Uninstall and reinstall of Visual Studio. The next morning the matches were working again with no issues and I haven't had a problem since.
Has anyone encountered anything like this before?
Accepted Solution
Ascension Health
US
Time to close this post. In the end I believe my problem may have been version control of the executable I was interrogating. I think someone slipped in a change that resorted the frames of the page and then reset them in the next version.
Ascension Health
US
No rollback and no re-image. I left the machine on overnight and when I returned in the morning to try again it was working? It's been well over 10 working days and I've had no recurrence.
Accepted Solution
Ascension Health
US
Time to close this post. In the end I believe my problem may have been version control of the executable I was interrogating. I think someone slipped in a change that resorted the frames of the page and then reset them in the next version.