Windows 10: Latest builds of Windows 10 and Server 2016 results in many Code 15 errors

We work in a medical software environment. Many sites are moving to the latest versions of Server and clients due to end of life. We are seeing sites reporting a significant increase CODE 15 errors which is an ERROR_INVALID_DRIVE 15 (0xF) The system cannot find the drive specified. The environment is the Application server and Terminal Server for RDP are both 2016. Windows 10 version 1803 build 17134.523. Using a Windows 7 client does not get any of this code 15 errors. Using the RDP client on the 2016 server produces these errors also. We have tried to add keepalive in the registry without improving the issue. This does occur usually during idle time connected to the database on the application server. I cannot reproduce this on windows 10 version 1709 to the application server 2016 version 1607. I am concerned as many sites will be upgrading to the latest windows versions and we are getting these reports early.


One of the sites reported resolving these by upgrading a 2008 r2 server they were using for Terminal servers to 2016. This site is not using Windows 10 as clients only the rdp for the application client. Does anyone know what in the registry would cause this increase of code 15 erros and it seems to be around idle time?


Resolution/Workaround at the site:


I have come up with a way to work around the issue and have resolved the code 15 errors which resolved the user's issues. I took a 2008r2 server installed the medical application and upgraded the OS and everything seems to work. I'm assuming that something comes along in the registry that makes everything happy, we have most of our users moved to the new server.

:)

 

What is the latest stable build of Win10 ?

If your not willing to run the latest V1803 build then I'd suggest sticking to v1709 from here http://windowsiso.net/windows-10-iso/windows-10-creators-update-1709-download-build-16299-15/ pick the one most applicable to you

 

Windows 10 BSOD Errors to Come with Troubleshooting QR-Codes

With its latest Preview Build (build 14316), Microsoft patched Windows 10 to make BSOD (blue-screen of death) errors more useful for system analysts and power-users. The blue-screen now puts up a QR-code to the knowledge-base page related to the error. Microsoft also set up an easy to remember URL at "windows.com/stopcode" for quick-reference to info and possible fixes to various kinds of errors.

The Register makes a valid case for how QR-codes in BSOD screens can be misused by malware developers. Malware or ransomware developers can now make their wares fake a BSOD screen with a QR-code that leads to their web-page to steal your information, or point you to download even more malware.





Source: The Register

 

Windows 10 will not activate Error code 0x803F7001


Possibly there can be the problem with Microsoft activation Server, so your Windows 10 is not activated. In this scenario, you need to wait and verify if it is the issue from Microsoft’s side. But if you are getting error code 0x803f7001, you can also try these steps:

1. Open Settings app. Then go to Update and security > Activation screen > Change product.
2. Type your Windows edition product key and click Next.
3. You’ll get We couldn’t activate Windows error message.
4. Retry steps 1-3 then type your 25-characters unique product key.
5. Wait for the process to complete, Windows 10 is activated.

Hope something helps this problem