We understand that support for Windows 10 will not be available until the next RM/COBOL release.
In the meantime, we have customers that may not heed our advice to wait before upgrading to Windows 10, and inevitably new machines with Windows 10 will be purchased.
So, in our testing of the Windows 10 upgrade, we were happy to notice that BIS continued to work after the upgrade. Then as an additional test, we uninstalled BIS and attempted to reinstall. The attached screenshot shows the result.
Is there a possibility of a workaround so that we can deal with Windows 10 before the next RM/COBOL release?
Tom Morrison
Hill Country Software and Support
#XBISWindows10#BISHi Tom:
This is a problem with the Windows installer. Microsoft jumped the IIS version number from 8.5 to 10; unfortunately, the Windows Installer is only capable of performing string comparisons on properties (even DWORDs), so the IIS condition check in the Xcentrisity BIS installer believes 10 is less than 5. Go figure!
The only way to fix this is with a new release.
As a very unofficial workaround that should be used only by someone familiar with the registry: on Windows 10, you can temporarily change the IIS version from 10 to 9, install Xcentrisity BIS, and then (very important) set the version number back to 10.
To do this, start REGEDIT and, in the following registry key:
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\W3SVC\\Parameters
Change the "MajorVersion" value from decimal 10 (or hexadecimal "A") to 9, then install Xcentrisity BIS.
Once the installation is complete, change the value from 9 back to decimal "10" or hexadecimal "A" (be sure you don't mix these up or hilarity will ensue).
For experienced users, this command will change the IIS version number from 10 to 9 from an administrator command line:
reg add "HKLM\\SYSTEM\\CurrentControlSet\\Services\\W3SVC\\Parameters" /V "MajorVersion" /T REG_DWORD /D 9
This command will set it back after the install (it’s very important to do this):
reg add "HKLM\\SYSTEM\\CurrentControlSet\\Services\\W3SVC\\Parameters" /V "MajorVersion" /T REG_DWORD /D 10
The command will prompt to overwrite the value; add /F to the command to suppress the prompt.
Again, this is very unofficial -- please wait for 12.11 before any deployments on Windows 10.
A second problem that you might encounter on development machines: in preview versions of Windows 10, the EDGE browser cannot access loopback addresses like "localhost" or "127.0.0.1" by default because of new security restrictions.
In preview releases, this one-time command allows EDGE to access loopback addresses:
CheckNetIsolation LoopbackExempt -a -n=Microsoft.Windows.Spartan_cw5n1h2txyewy
There was much complaining from developers about this problem, so It's possible that Microsoft resolved this problem in the actual release. It's also possible that the code above changed, and this trick might not work any longer.
There is no problem with Internet Explorer, Firefox, or Chrome on Windows 10 -- only EDGE has this restriction.
#XBIS
We understand that support for Windows 10 will not be available until the next RM/COBOL release.
In the meantime, we have customers that may not heed our advice to wait before upgrading to Windows 10, and inevitably new machines with Windows 10 will be purchased.
So, in our testing of the Windows 10 upgrade, we were happy to notice that BIS continued to work after the upgrade. Then as an additional test, we uninstalled BIS and attempted to reinstall. The attached screenshot shows the result.
Is there a possibility of a workaround so that we can deal with Windows 10 before the next RM/COBOL release?
Tom Morrison
Hill Country Software and Support
#XBISWindows10#BIS"please wait for 12.11 before any deployments on Windows 10"
You seem to think we have some control over this! Our customers are just as unruly as yours are. 
Thanks for the reply, Uwe. That gives us an idea about how do this.
Also, appreciate the heads up on Edge. Of course, the same customers that will be installing our product on desktop systems will by that very fact be using the loopback address. We probably have other issues with Edge, but you have given us at least one rung up the ladder.
