tracker issue : CF-3984812

..........................................................................+1

Vote by External U.

+1 Now that I actually have Windows 10 installed, this has become an urgent issue.

Vote by External U.

+1 15 Days to go!!! Please explain in 25 characters

Vote by External U.

Will be following up on this one. Thanks Stephen.

Comment by Immanuel N.

IIS 10 to be released on July 29…58 days to get wsconfig to work

Vote by External U.

Upon applying Web Server configuration of CF 11 on IIS 10, an error warning prompt appears and aborts the configuration process - "Version 10.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x"

Comment by External U.

+1 .

Vote by External U.

Please Adobe, get hot on this one. This is pretty much a deal-breaker for me to migrate to Windows 10.

Vote by External U.

Any solutions yet that I missed? I upgraded to Windows 10 (currently available for PUBLIC RELEASE ) and now CF11 is broken...

Comment by External U.

I've upgraded my laptop to Windows Ten and I'm unable to do Dev work with CF11 on it. I'm hoping you've already fixed this issue, but if not, now would be a really, really good time to do so.

Vote by External U.

+1 Please Please Please Please

Vote by External U.

+1.. we need this hotfix ASAP

Vote by External U.

This should be a priority. We have to certify our development tools and cannot do so because of this issue.

Vote by External U.

+1 looks like many of us are in the same boat

Comment by External U.

A hot fix would be greatly appreciated

Vote by External U.

It seems that the value of the ColdFusion does not consider the solution of this problem! The problem should have been resolved in June / 2015.

Comment by External U.

Unable to improve the development environment.

Vote by External U.

Also, fixing Windows 10 will also likely lay the groundwork for adding support for Windows Server 2016 when it is released.

Comment by External U.

Is there anything happening on this one? 150 Million users have upgraded to Windows 10 after July 29. CF...Guys, pl help...You need to find a way to install and development should be able to continue on Windows 10 Really disappointing...as this would have been ideally done months back with Tech Preview version

Comment by External U.

Someone said Right.... Do we need to VOTE?....NO. THIS NEEDS TO BE FIXED AT SOURCE (Which is Adobe)

Vote by External U.

Any solutions for this? we need this hotfix ASAP....

Comment by External U.

This fix is important for us to continue our CF development. Please fix it ASAP

Vote by External U.

+1.. we need this hotfix ASAP

Vote by External U.

Why hasn't this been addressed yet Adobe? You could have gotten ahead of this with the months of Windows 10 preview releases and had it ready for the actual release. You are continuing to disappoint your developers time and time again. No wonder so many are changing to other languages. This is now a roadblock for our dev shop as well.

Vote by External U.

Need this fixed ASAP. Already causing problems in development.

Vote by External U.

I need this or a work around NOW! PLEASE release a hotfix asap!

Vote by External U.

I and a at least 10K other developers will need this ASAP! Broken my development environment. In crunch mode too for our application. SUCKS!

Comment by External U.

PRIORITY NEEDS TO BE SET TO URGENT. THIS IS NOT AN ENHANCEMENT BUT A COMPATIBILITY FIX. DON"T YOU GUYS TEST YOUR SHIT ON THE WORLD'S LEADING OS's PRE-RELEASES WHEN YOU CAN. BY THE WAY, CANNOT CONFIGURE THE LATEST APACHE SERVER with WSConfig either! SUCKS!!!!!! :-(

Comment by External U.

Has anyone from Adobe even acknowledged the issue? It would be nice to here from and Adobe representative.

Comment by External U.

I'm dependent on ColdFusion for its implementation of WebSockets. We recently upgraded to Windows 10 and now the configuration tool no longer works. As a side note, Lucee/Railo doesn't have this issue and ported over perfectly. Their websockets implementation isn't as good, but if it takes Adobe too long to get this updated I might as well work on improving the Lucee websockets so I won't run into this dependency again.

Vote by External U.

There is a workaround in the meantime: https://helpx.adobe.com/coldfusion/kb/coldfusion10-iis-manual-connector-configuration.html

Comment by External U.

rohit, is the workaround tested for CF11? Have you had success? -Thanks.

Comment by External U.

I have not tested for CF 11, but considering what is involved with workaround and both CF 10 and 11 run on Tomcat I am pretty sure it will work for CF11.

Comment by External U.

We are working on this issue. Refer to this blogpost for details. http://blogs.coldfusion.com/post.cfm/configuring-connectors-manually-for-iis-10

Comment by Chinoy G.

Same problem here with the workaround not working, can we have some input Adobe please?

Comment by External U.

jar extraction runs on wsconfig.jar without error but extracts no file... Running in Windows 10...

Comment by External U.

Adobe really IS trying to KILL ColdFusion! This is even more proof.

Vote by External U.

+1 ......................

Vote by External U.

Colin, what is the error you are getting after applying the workaround.

Comment by Chinoy G.

Nathan, Can you share the wsconfig,jar that you have.

Comment by Chinoy G.

Need fix to run Developer version under Apache also!

Vote by External U.

+1 The workaround does not work either.

Comment by External U.

Looking for Win 10 support

Vote by External U.

Adobe Team should be embarrassed that this is still an issue when 10 has already been out for weeks.

Vote by External U.

Sergio, Can you provide the connector config and log files.

Comment by Chinoy G.

Chinoy, I uploaded the jar file days ago. Nathan

Comment by External U.

I just attached my entire config directory. >>>

Comment by External U.

FYI - I have done this a few times, and every time I end up at "HTTP Error 404.17 - Not Found". I have spent about 50 hours on this over the past two weeks and have tried everything I can think of. Has ANYONE gotten the manual workaround to work yet? Also, I upgraded another PC which already had CF11 on it and it is still running correctly. But I noticed that if you attempt to run the Web Server Config Tool, it will DELETE your wsconfig/1 folder.

Comment by External U.

Sergio, Can you enable debug logs in connector and make some requests. and then share the logs

Comment by Chinoy G.

Nathan, where did you upload the jar file? I am not able to find it in this bug's attached files.

Comment by Chinoy G.

I didn't know I had to zip it up.

Comment by External U.

Nathan, I am able to extract the jar and see all its contents including prebuilt connector binaries.

Comment by Chinoy G.

I would like to chime in here with the others to urge Adobe to update their ColdFusion 10/11 installer to support the release version of Windows 10. But in the meantime, give us the manual installation directions to get ColdFusion working. This is very important.

Comment by External U.

When I try to extract just the isapi_redirect.dll by itself it doesn't show up, but I am running it on Windows 10?

Comment by External U.

I was able to manually configure the connectors using the steps in https://helpx.adobe.com/coldfusion/kb/coldfusion10-iis-manual-connector-configuration.html But each request seems to be *very* slow. Like 10 seconds even for a simple/trivial request.

Comment by External U.

Please fix this asap. (extra characters to get over the 25 minimum...)

Vote by External U.

Chinoy, I have enabled debug logs in isapi_redirect.properties and have made multiple requests, but a isapi_redirect.log file is never generated. Here is all I continue to get: HTTP Error 404.17 - Not Found The requested content appears to be script and will not be served by the static file handler. I have attached my most recent "config" and "logs" folders.

Comment by External U.

Sergio, did you add the handler mappings in IIS website as mention in #6 of the KB article?

Comment by Chinoy G.

I was able to extract the dll by extracting the whole jar file to a separate folder. I followed the directions in the two documents mentioned, and I am getting a 500.x error now.

Comment by External U.

Yes, I have all of the correct mappings. When I remove them, I receive a different error: HTTP Error 404.3 - Not Found The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map. I also determined that I receive the same 404.17 error whether the CF server is running or not, so it's as if the CF server isn't even there.

Comment by External U.

After further fiddling, if I go to Application Pools > DefaultAppPool > Advanced Settings and change Enable 32-Bit Applications to FALSE, I then receive a new error: HTTP Error 500.0 - Internal Server Error The page cannot be displayed because an internal server error has occurred. But stopping the CF Server still has no effect on the error.

Comment by External U.

I need this, along with everyone else, ASAP. This should have been ready BEFORE Win 10 was released. This is inexcusable.

Vote by External U.

Wow, do we really need to vote on something as obvious as this? Apparently so.

Vote by External U.

Please fix this issue as fast as possible. I had to reinstall windows 8.1 on another machine just so I can test code.

Vote by External U.

I followed the instruction given by Rohit S on the helkp thread https://forums.adobe.com/thread/1898715... I still get the following error: HTTP Error 500.0 - Internal Server Error The page cannot be displayed because an internal server error has occurred. Most likely causes: IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed. Things you can try: Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. Detailed Error Information: Module IsapiFilterModule Notification AuthenticateRequest Handler ExtensionlessUrlHandler-Integrated-4.0 Error Code 0x80070001 Requested URL http://127.0.0.1:80/ Physical Path C:\inetpub\wwwroot Logon Method Anonymous Logon User Anonymous This is CF11 on Windows 10 professional 64 bit.I get this when i try to go to 127.0.0.1 for the first time after installation for the configuration part in the browser right after the setup program runs. Let me know if there is any other logs or other files i can include to help. Eric Roberts Sr. ColdFusion Developer Three Ravens Consulting

Comment by External U.

I think some of my probles were config ones...I missed a couple of {magic number}'s and hadn't replaced them with the number 1. So after i got all of those cleared up I got the following errors: This is in the isapii_redirect.log file: [Thu Aug 27 09:51:47.789 2015] [14400:25916] [debug] handle_notify_event::jk_isapi_plugin.c (2404): [/] is not a servlet url This is the IIS error displayed in the browser: HTTP Error 404.3 - Not Found The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map. Most likely causes: It is possible that a handler mapping is missing. By default, the static file handler processes all content. The feature you are trying to use may not be installed. The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.) If ASP.NET is not installed. Things you can try: In system.webServer/handlers: Ensure that the expected handler for the current page is mapped. Pay extra attention to preconditions (for example, runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool. Pay extra attention to typographical errors in the expected handler line. Please verify that the feature you are trying to use is installed. Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe. To set a MIME type, use the following syntax: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticContent /+[fileExtension='string',mimeType='string'] The variable fileExtension string is the file name extension and the variable mimeType string is the file type description. For example, to add a MIME map for a file which has the extension ".xyz": appcmd set config /section:staticContent /+[fileExtension='.xyz',mimeType='text/plain'] Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them. Install ASP.NET. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. Detailed Error Information: Module StaticFileModule Notification ExecuteRequestHandler Handler StaticFile Error Code 0x80070032 Requested URL http://127.0.0.1:80/index.cfm Physical Path C:\inetpub\wwwroot\index.cfm Logon Method Anonymous Logon User Anonymous More Information: This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files. View more information »

Comment by External U.

I can't help but noticing that the bug status has been changed to FIXED and has been sent to test. Can testing be expedited and a hotfix released ASAP?

Comment by External U.

PLEASE!!??

Comment by External U.

I am now getting partial usability from CF. I readded the handler mappings and made sure they all had execute permissions. Now I can get to the index page of my site, but when i click on any link to go to another page in my site, I am served a blank page. The view source has no code. The index page uses CF functionality like includes and other CF tags, so it's not like it is straight html...it is also slower than molasses in January. A page that should come up in less than a second takes about 10-20 seconds to come up. It's not a hardware issue. My machine has an 8 core processor and is 4ghz with 32 gig ram and plenty of drive space...something is not right. How is it that this was not tested on the pre-release of Windows 10? Come on guys...we expect better than this. I am not seeing any errors...I am going to dig into the logs and see if i can find anything there. If i do, i will post...

Comment by External U.

I have uploaded my isapi-redirect.log file...this is the only error I could find... [Thu Aug 27 13:58:48.301 2015] [25328:30348] [error] HttpExtensionProc::jk_isapi_plugin.c (2622): failed to init service for request.

Comment by External U.

*writing in the dust* FIX ME PLEASE!!!

Vote by External U.

Is there anyone from Adobe really looking in to this. We are all trying around the way which in first should be solved by Adobe. Where are you people from Adobe?????

Comment by External U.

Guys, Please help to fix this one. Is there any way out? need solution... ASAP.

Comment by External U.

+1 Hotfix needed Urgently...

Vote by External U.

Need this fixed ASAP. Already causing Major problems in development.

Comment by External U.

Eric, there are no files inside the isapi_redirect.zip you uploaded. Can yiu upload it again and before capturing the connector logs, enable debug logging.

Comment by Chinoy G.

Chinoy, have you taken a look at my latest file/problem? This is going nowhere fast.

Comment by External U.

Has anyone had confirmation of Adobe working to fix this?

Comment by External U.

Good Point Kelton, Is there anyone from Adobe evening looking in to this. W10 has already matured and plenty of PC/Laptops are getting upgraded... Where is the FIX Adobe Guys????

Comment by External U.

Status to the right side of this bug has been showing fixed - ToTest for over a week. So how long is it going to take to get a hotfix patch?? Chinoy?

Comment by External U.

Never thought that adobe wouldn't support Windows 10 for CF. Adobe, need support for this ASAP....

Comment by External U.

Yes, Nathan...That was a good pick. Is Adobe going to replace the installer? Anyone from Adobe????

Comment by External U.

Needed to reinstall CF11 fresh after Windwos 10 install. Everything for installer goes to plan, then when attempting to apply Web Configuration tool to CF11 i get presented with - "Version 10.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x". This just needs to be fixed Adobe...

Comment by External U.

Has anyone been able to install any version. George mentions the supported versions in his message when attempting to config CF11. Right now any version would suffice compared to no versions. This is beyond inconvenient.

Comment by External U.

Maybe we can try the request again. I entered the bug into the adobe site and everyone could vote on it immediately. Maybe, just maybe it would garner attention then. If you all don't mind. Go to the "ticket" and vote on it. This is ridiculous to have to do, but I can't keep waiting and hoping. Vote on this global issue and game changer for CF developers. https://bugbase.adobe.com/index.cfm?event=bug&id=CF-4050165

Comment by External U.

No developer of CF can work with Windows 10 and CF (any version)

Vote by External U.

is this fixed? it's totally urgent!

Vote by External U.

Need Windows10 support for CF11 ASAP

Vote by External U.

September rolled over, and still no official fix released? The ticket status update of "fixed"/ "ToTest" is promising though..

Comment by External U.

Yes, Its promising to see as "Fixed" :) How do we proceed...Can anyonw advise? Will this relase a new Installer? Or a patch?

Comment by External U.

Chinoy (Adobe Rep) has completely abandoned this thread. This is embarrassing.

Comment by External U.

Is this true??? Should we stop using CF???? on Windows 10 in that case?

Comment by External U.

I'm already on windows 10 and would like to be able to use CF again

Vote by External U.

To someone, anyone with ColdFusion support: When will we get this fix released to us? It is seriously hampering my work, and the work of many others. If our applications were not so invested in ColdFusion, I would abandon Adobe entirely...

Comment by External U.

Hi Everyone, There is no update on Installer yet...Its very much same. Can someone from Adobe reply on this status...When would you be able to update the Installer? Thanks...

Comment by External U.

Please provide a fix and/or an update to this ticket!

Vote by External U.

This is actually Nathan Manning. I thought this was inTest, had a high priority, and most certainly is Not an enhancement. Frequency is every attempt, not unknown. When in Hell will this be fixed and released? Terribly disappointed. Planning a future release of our Application that ABANDONS

Comment by External U.

Do you want us to ABANDON ColdFusion as a platform for our products???

Vote by External U.

I mean JESUS CHRIST GUYS. IT'S ALMOST 2016.

Comment by External U.

Seriously. This is it. We're going to plan a migration away from ColdFusion. You guys are embarrassing us and yourselves. Windows 10 has been out for months.

Vote by External U.

This is critical! Why do my existing sites run fine after the Windows 10 upgrade, but I can't add new sites? This is just...unbelievable. I had no idea this was going to be a problem. Really, really, really need a TOP PRIORITY on this!

Comment by External U.

I had emailed Anit Kumar Panda, Coldufsion Senior Consultant on 9/8 this: There is a lot of momentum surrounding the incompatibility of CF11 on IIS10/Windows 10. This thread seems to have a lot of unanswered questions and frustrated people. Is there any way we can get a definitive response? This was his response...still very vague. Windows 10 is not yet certified with ColdFusion. Please refer to http://blogs.coldfusion.com/post.cfm/configuring-connectors-manually-for-iis-10 for more info. Thanks & Regards Anit Kumar Panda | Senior Product Consultant - ColdFusion | Adobe My recommendation if you need to run CF11 on Windows 10 for development purposes, is to run CF11 within Windows 10 on a <= Windows 8 Virtual Machine. Not ideal and requires more hardware resources but it works and allows you to move forward into Windows 10.

Comment by External U.

KVN, sure, I don't have a problem with "certification". Whatever. But let us add the sites so we can tell YOU if there's problems. Just release an update to the wsconfig.jar that doesn't limit through version 8 of IIS. If the syntax is the same (and I think it is), just let it run.

Comment by External U.

This is really more of an issue in enabling the web configuration tools to recognize IIS10. I believe if that were done, it would work just fine. Why all the hassle? Politics between Adobe and Microsoft?? Edge doesn't allow plugins? What????

Comment by External U.

When Windows 10 was prereleased it has IIS8 and was fine with CF11. Once it was updated to 10 and packaged with the primary release it broke. I've tried reverting IIS in Windows 10 to no avail as well.

Comment by External U.

Just release the source code for the wsconfig.jar. Nothing "super duper proprietary" in there. Then we can do what we need to do with a modification to it.

Comment by External U.

What I meant to say earlier was that "this is NO MORE of an issue in enabling the web configuration tools to recognize IIS10." Everything else I have, use, and build works perfectly with IIS 10 and Windows 10. We developers waited a long time for Windows 10, staying on 7 Ultimate or Pro because Windows 8/8.1 sucked for development. Now we need you to step the f@#k up.

Comment by External U.

If the status is closed/fixed where can we get the update?

Comment by External U.

Fixed / Closed? I see attachments on the right, but would like at LEAST a message from Adobe here? Gotta say, Adobe...the follow up is just...lacking, guys. I wonder if the Photoshop department works this way?

Comment by External U.

OMG does this work now? Not seeing any updates available in Server Updates.

Comment by External U.

OH WAIT. FOUND IN CF11_FINAL???!?!?!? IS IT NOT COMING TO CF10?????

Comment by External U.

David, Were did you find it?

Comment by External U.

Where is the HOTFIX????

Comment by External U.

Will this fix be found in the public download? https://www.adobe.com/cfusion/tdrc/index.cfm?product=coldfusion

Comment by External U.

I didn't find it, it says Found in Build CF11_Final in the build panel to the right of this note.

Comment by External U.

The status was just again changed to Fixed/Closed so I downloaded the latest build and it still DOES NOT WORK. Same error - "Version 10 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x". This is the 3rd or 4th time this issue has been re-opened and re-closed with absolutely no update, reason or response from Adobe. Adobe has no clue what they are doing, and is intentionally leaving everyone in the dark. The Adobe team also completely abandoned this thread months ago because they have no answers, nor are there any in sight. Apparently Windows 10 was built with pixie dust, unicorn tears and magic, and there is no possible way to run ColdFusion on it. In the meantime, with all of this spare time on my hands, I have been searching for a ColdFusion alternative and have found a much better and fully supported product called Railo. And GUESS WHAT? It supports Windows 10! You can find it here - http://www.getrailo.org Here is also a great article outlining Adobe's negligence and complete disregard for their customers - http://www.webtrenches.com/post.cfm/why-we-may-be-moving-from-adobe-cf-to-railo Goodbye Adobe. And good luck retaining customers.

Comment by External U.

Sergio, they have nothing in "Fixed in Build". So they have not published it yet.

Comment by External U.

The fix would be included in the next update. However we have made an early access version available which you can use for development. The details are available at http://blogs.coldfusion.com/post.cfm/running-coldfusion-10-and-11-on-windows-10

Comment by Rupesh K.

EEEEEEEEE! Hope this works. Thanks Rupesh. Better late than after we retire.

Comment by External U.

Important! FYI, this update requires ASP.NET 3.5 and/or 4.6, it did not work w/ regular old ASP enabled. But after enabling both and restarting Win 10 it seemed to work. Halelujah.

Comment by External U.

Somehow, index.cfm doesn't seem to work but other URLs do. As long as I use a non-index.cfm default document it seems to work, otherwise it seems to be using a random index.cfm from elsewhere. Is anyone else hitting this issue?

Comment by External U.

Hmm, it seemed to use the index.cfm of the built in wwwroot for CF if that was there, and then would use the index.cfm of the current site if not. Deleting that file seemed to fix it. This may be related to my having installed CF originally knowing that it struggled w/ Windows 10 w/ the built in web server ( 8500 ). Is there a way to turn that off / remove that post-install or do I have to fully uninstall and reinstall?

Comment by External U.

hello, I followed the steps in http://blogs.coldfusion.com/post.cfm/running-coldfusion-10-and-11-on-windows-10 I can run the server configuration now, the handlers are created in the IIS, but I get HTTP Error 500.0 - Internal Server Error for cfmHandler. Am I missing another configuration ?

Comment by External U.

I can report that it is working for me now, so far. I still can't understand why this took so long to get done.

Comment by External U.

I have windows 64bits and I downloaded the coldfusion 64bits. restarting the IIS enables the option 32bits application to true in the defaultAppPool, it will give the 500 error for the index.cfm page. when I put it to false, the index.cfm is downloaded. It should at least behave the other way around, no ?

Comment by External U.

@Nathan how did you finaly the solution? I still get a 500 error... thx Stefan

Comment by External U.

Even when following the manual configuration article we were unable to make cf 9 or 11 work with iis 10. We hope a fix can be made soon.

Vote by External U.

There has been some reported success to work around the wsconfig issue using BonCode. A developer peer of mine was able to make this work with IIS10. https://www.youtube.com/watch?v=Ps4zLOKmGY0 I hope to try this later today on another development machine (Windows10 IIS10). I'll post with any success or failure. If anyone else tries this approach, please post if you are successful with any tips for other developers.

Comment by External U.

HEre's the contents of my WSCONFIG.log # Created by ColdFusion on 11/23 14:57:00 11/23 14:57:00 info Tomcat Connector 11/23 14:57:00 debug Created file C:\ColdFusion11\config\wsconfig\cfwin32.dll 11/23 14:57:00 debug Created file C:\Users\eroberts\AppData\Local\Temp\\ExecuteAppCmd\ExecuteAppCmd.exe 11/23 14:57:00 debug command line: -ws IIS -site 0 -cfide C:\ColdFusion11\cfusion\wwwroot\CFIDE -v 11/23 14:57:00 info Version 10.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x 11/23 14:57:00 error Version 10.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x com.adobe.coldfusion.connector.connectorinstaller.WSVersionNotSupportedException: Version 10.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x at com.adobe.coldfusion.connector.connectorinstaller.IISInstaller.installConnector(IISInstaller.java:157) at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.installConnector(ConnectorInstaller.java:355) at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.doIt(ConnectorInstaller.java:299) at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:762) 11/23 15:12:08 info Tomcat Connector 11/23 15:12:08 debug Created file C:\ColdFusion11\config\wsconfig\cfwin32.dll 11/23 15:12:08 debug command line: -ws IIS -site 0 -cfide C:\ColdFusion11\cfusion\wwwroot\CFIDE -v 11/23 15:12:08 info Version 0.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x 11/23 15:12:08 error Version 0.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x com.adobe.coldfusion.connector.connectorinstaller.WSVersionNotSupportedException: Version 0.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x at com.adobe.coldfusion.connector.connectorinstaller.IISInstaller.installConnector(IISInstaller.java:157) at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.installConnector(ConnectorInstaller.java:355) at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.doIt(ConnectorInstaller.java:299) at com.adobe.coldfusion.connector.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:762) THe error I get is Calling LoadLibraryEx on ISAPI filter "F:\ColdFusion11\config\wsconfig\1\isapi_redirect.dll" failed I get this when CF goes into setup mode right after the install. This has been a problem for a long time. When is this going to get fixed? This is getting to the point where it is unprofessional. Are you guys just trying to kill CF?

Comment by External U.

Hi Eric, Can you please follow steps provided in below link : http://blogs.coldfusion.com/post.cfm/running-coldfusion-10-and-11-on-windows-10 Thanks, Mukesh

Comment by Mukesh K.

I got it to work before this latest blog entry and had to extract the wsconfig.jar from a larger jar. I had to extract them all into a separate directory to get the wsconfig.jar because for some reason going after a single jar in the lib wouldn't work for me win10. I think the latest mentioned blog gets you just that jar file, so you shouldn't have that problem. One caveat is that since CF11 is already installed, it will only install the Admin IDE in Jakarta under the Tomcat server, but once you run the connector utility, the rest of your apps will work with IIS 10. Also, before I did all this I removed both IIS and CF11. Did a clean install of both, IIS first, and then replaced the jar and finally ran config. It's working fine for me. Hope that helps...

Comment by External U.

where is CF11_Final

Comment by External U.

I cannot install CF11 on windows 10. Fifth attempt. I have even installed the latest update hotfix_009. No admin page displays. I ran the web config manually. No luck!!

Comment by External U.

Hi Adobe, I've verified this is fixed in CF2016 Update 1 (build 2016.0.01.298513). Thanks!, -Aaron

Comment by Aaron N.