Good news, everyone: Windows 10 Creators Update has been officially released today, and it’s now available for download on the Microsoft website. The new version adds a handful of new features and improvements to the operating system, including Windows Ink and advanced security settings, and is reported to be the most significant Windows 10 update as of yet.
However, there’s still a fly in the ointment. Windows developers, beware (actually, end users should be aware of this, too).
Our dev team has run an in-depth test of the new Windows 10 Creators Update, and here’s what they’ve uncovered.
When you use the CreateService() function to create a Windows system service, specify the SERVICE_WIN32_SHARE_PROCESS for the dwServiceType parameter, and provide command line arguments that contain mixed or uppercase characters within the lpBinaryPathName argument, you’re most likely to encounter an unexpected effect.
When these arguments are passed to your system service module in an lpCmdLine parameter of the WinMain entry point, they will be entirely lowercased. This means that you may encounter unexpected issues if your application relies on case-sensitive arguments. Please note once again that this will occur only if the SERVICE_WIN32_SHARE_PROCESS value is used for the CreateService API call.
We understand that most well-designed applications don’t rely on case-sensitive arguments. However, we believe that this tiny change may surface for some applications in a most unexpected way. We were quite astonished when we found this, to say the least, as never before in the long Windows history has such a change been witnessed.
If you happen to provide support to users who have already switched to Windows 10 Creators Update, don’t hesitate to try out the FixMe.IT remote desktop application for remotely fixing any issues that may arise.