Important update: Note that ColdFusion 10 and 11 have been updated to support Windows 10, a few weeks after this blog post was first written. Consider applying that update rather than this preliminary wsconfig update.
Windows 10 is not certified yet with ColdFusion 10 and 11. The certification will be available as part of the next update. However, you can run ColdFusion 10 or ColdFusion 11 on your development environment by following the below outlined steps.
ColdFusion 11 32-bit/64-bit
1. Please take a backup of the existing wsconfig.jar at ColdFusion11cfusionruntimelib and move it outside ColdFusion directory.
2. Stop the ColdFusion services and remove the older wsconfig.jar.
3. Download the jar files from the links above.
4. Place them in the location mentioned in Step1 and restart IIS/ColdFusion.
5. Please take a backup of the connector folder at ColdFusion11configwsconfig[magic number].
6. Recreate the connector and test your application.
ColdFusion 10 32-bit/64-bit
1. Please take a backup of the existing wsconfig.jar at ColdFusion10cfusionruntimelib and move it outside ColdFusion directory.
2. Stop the ColdFusion services and remove the older wsconfig.jar.
3. Download the jar files from the links above.
4. Place them in the location mentioned in Step1 and restart IIS/ColdFusion.
5. Please take a backup of the connector folder at ColdFusion10configwsconfig[magic number].
6. Recreate the connector and test your application.
In case you will have any questions please feel free to contact us at cf.install@adobe.com and we will be more than happy to assist you.
Staff
109 posts
Finally got it work by downloading hotfix jar file then running upgrading in the command mode, and at last, re-running configuration tool.
Please advise, what credential to use to get that jar file?
Why should someone have to configure CF10/11 to use the Internal server, apply patches, then reconfigure CF for IIS when Adobe has clearly posted two JAR files that fix the issue? If they would just give people the login info to download the jar file they need or allow anonymous login, people would be able to fix it without needing any assistance or having to go through multiple reconfigurations. Goodness, it’s that simple. Thanks Adobe!
Actually, for some reason on my new laptop the CF 10 installer just fails before it even starts. Is there an official Adobe link to the latest CF10 build online somewhere?
The problem is you can’t get to a CFIDE to apply an update if your install of CF 10 isn’t successfully connected to your IIS site, so I need the update connector file first :'{
The download links don’t work, asking for username and password.
Hi Trena,
Can you please share your contact details on cf.install@adobe.com ? We will get in touch with you.
Thanks,
Rahul
How many connection pools should I have for 5 sits with multiple users on each. There are times inn the month where the traffic will be high. Right now it keeps crashing. I keep getting a 5002 or 5009 event.
What did work for me though is get a copy of the file from a working box. Allowed me to use the web server configuration tool to create the connector. Maybe might help someone who finds themselves reading it in the future.
I think I fall in the middle. I downloaded CF 11 Quite a while ago which means I need the jar file but can no longer get it.
@Scott, I agree. Seems like every time another version of CF comes out months after a new OS is released, you have to jump through hoops trying to get it to work if at all.
Link is broken, cannot download the updated jar file.
Hi Charlie,
What both you and Adobe have probably missed here is the fact that if you are installing on Windows 10 then in order to install the stated update, you need to access the cfadmin, but in order to access the cfadmin you need the update to get the connector. So it is a catch 22 unless you know how to work around it.
Luckily I do know how to work round it, so I simply enabled the internal web server and used that instead to get the update.
But for someone who is new to CF and not savvy with the server side of things, this would have caused a major headache.
the link to download the updated wsconfig requires authentication, what are the login details ? I do not see them mentioned anywhere in this post.
Hi All,
The links are fixed now.
I successfully installed the hotfix (wsconfig.jar) and ColdFusion is running now on Win 10, but the Configuration and Settings Migration Wizard hangs after I log into CFIDEAdministrator so with no way to configure I am still broken.
Suggestions?
@Mike,
The plan looks absolutely fine. The latest web server configuration tool(wsconfig.jar) which is supported in Windows 10 is part of our next update and is available online for testing purpose.(link:https://coldfusion.adobe.com/post.cfm/coldfusion-11-update-7-is-available-for-early-access). Please let me know if you have any further queries.
Thanks,
Vikram
I am thinking about what to do next in my case. I have several more machines to upgrade to Win10 as well. I think my problem was that i was trying to change too many things at once. Instead, for my other machines I think i will:
(a) remain at Win7/CF9 for now, (which is what I have on my production servers),
(b) change from Apache to IIS (which is the web server on my production servers), then, when that’s working satisfactorily,
(c) upgrade from CF9 to CF11 (while it’s different to my production servers, CF9 is apparently NEVER going to work with Win10), then, when that’s working satisfactorily, and ONLY then,
(d) go to Win10.
I think that will give me much better odds of it all working properly, because at the last step, the only part of the CF/Windows combination that is in question is the wsconfig.jar.
What do you people think of that plan?
Please ignore my last comment. It works now. The hotfixes I installed later must have overwritten this new wsconfig.jar on the other instances. Thx.
I followed the steps here and it works for the default cfusion instance, and I can go to cf admin on port 80 via IIS no problem.
After I added a new instance, then I run C:ColdFusion10[instanceName]runtimebinwsconfig.exe, but it shows “Warning: Version 10.0 is installed. Supported versions are 4.x, 5.x, 6.x, 7.x, 8.x”.
I tried copying the new wsconfig.jar to C:ColdFusion10[instanceName]runtimelib and tried again, still gives me the same warning.
How to make this work with instances other than ‘cfusion’?
I find it funny that after the debacle with Windows 8, that Adobe still can’t be proactive and have all this ready for the updates to Windows 10.
Microsoft have what they call a preview program and Adobe would it no be within your best interest to apply to that program and actually be proactive and make sure your tools and software work on these releases in a more timely fashion.
The problem is Adobe is too old school for this modern world and unless something changes, they are going to continue to piss developers off to other languages.
@Shawn: That’s great. Thanks for the update.
@Rakshith
I got it fixed. I was using the jar from the previous example.The one you included here fixed it. Initial loads are now down to a respectable 2 seconds.
Worked for me. Finally. Only been waiting for like a year for Windows 10 compatibility.
@Mike,
Our team would get in touch with you. Alternatively, you can get in touch with us at cf.install@adobe.com
I’d use the cf install email for that one. Never had that issue before.
These instructions all seem to imply an already-installed CF11. But Mine wont install. It complains at the screen where I have to nominate the web server. Doesnt like the IIS choice. But when I try to install it using the built-in server it just hangs.
CUrrently, it’s been 30 minutes at 12% installation, saying “Installing – check for previous version(s) of COldlFusion.”
What now?
@Tamara, our team is already in touch with you regarding this issue.
Yeah a different bit setting could cause it. I’m running Windows 10 pro and mine does not change the bit support on restart. If your .cfm files are downloading, then they aren’t being handled properly. I would verify those are done correctly.
Also make sure you have the tomcat ISAPI filter added.
ISAPI Filters > Add
tomcat
CFPathconfigwsconfigmagic numberisapi_redirect.dll
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.
when I put it to false, the index.cfm is downloaded.
It should at least behave the other way around, no ?
I am going to purchase a laptop with windows 10 OS, and I was thinking that how I would be able to run so many applications on it, but now at least I can run coldfusion on Windows 10. Thanks for this article.
hello,
all of the above is done, but still the problem persists.
I hope it has nothing to do with my windows version :
windows 10 Home single language ?
thank you for the effort
I would make sure /CFIDE and /jakarta virtual folders exist.
If that doesn’t work, make sure ISAPI is enabled in Handler Mappings. On my install it was disabled by default, even after you install the feature. IIS could be better describing enable/disable.
Double click ISAPI-dll > Request Restrictions > Access > Execute translates to Enabled
If that fails maybe you are using an IIS module that is not installed like URL rewrite?
hello,
I followed the steps for coldfusion 11 64bits
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 ?
@Shawn: Thanks for the feedback. Our engineers will have a look at the issue that you have mentioned above.
@Aaron: Great. Thanks for the feedback.
I’ve confirmed cf.install@adobe.com does work. It didn’t in October of 2014, so I’m glad to see it works now.
Thanks!,
-Aaron
Hi Rakshith,
Does cf.install@adobe.com work now?
I thought only cf.instal@adobe.com (w/ 1 “l”) worked.
Just want to confirm – b/c “install” is the correct spelling but did not previously work.
Thanks!,
-Aaron
I have CF11 running on my SP3 with Windows 10, with all updates installed, however it appears to be very slow on the first load the application taking 8-10 seconds. This appears to mimic the earlier IIS bug minus the web.config file from getting corrupted when it changes.
You must be logged in to post a comment.
23 Nov
10AM Pacific
Online
