WinhostReviews of winhost.com

Response from WinhostJul 29, 2026

Thank you for your feedback. We understand how frustrating these issues can be. In both cases, our support team investigated the problem and worked to resolve it as quickly as possible. We appreciate your patience and want you to know we're always here to help whenever you run into an issue with your hosting.

Response from WinhostSep 21, 2023

We are happy to hear that you are enjoying the ease of use of our Windows hosting platform - especially being able to use tools like IIS Manager and SQL Management Studio. As for FTP speed, there is not a whole lot we can do about that as our servers are located in USA and you are located in Eastern Europe. While it may take a little more time in managing your site, I hope that your website speed is satisfactory.

Response from WinhostJun 15, 2022

We are sorry to hear that this customer was not happy. We offer the best support in the best way that we can and, if you check out the other reviews here, you will see that we have many customers that are happy with our hosting services and our great support. We hope that this customer finds a host that will provide them with the hosting style they prefer.

Response from WinhostOct 20, 2022

We are sorry to hear this customer did not like the way our subdomains feature worked. Our philosophy is to give the customer the most flexible system as possible and to put as much control in the customer's hand. The subdomain feature is available and is completely under the customer's control through their code rather than having to log in and interact with a control panel.

Response from WinhostMar 1, 2021

I'm sorry to hear that you are experiencing slowness for your application. There could be many reasons why this is happening. The best thing to do is to contact our technical support team and they can look into this matter and advise.

Response from WinhostSep 22, 2017

Hi David. First of all, we love you too, and we hear what you're saying. But we do support Framework-dependent .NET Core on the web servers. We recommend Self-Contained Deployment for anyone who wants to use very recent versions of .NET Core, because we'll never be completely up-to-date with those latest versions. The problem with Core form our perspective: their rapid development cadence is skewed toward virtual server "cloud" platforms like Azure that can be updated every few weeks or 10 days or whenever the Microsoft engineers feel like dropping the latest version. But on a traditional server platform like we run - we can't update a framework on a hundred servers every couple of weeks. It isn't feasible. And more than that, it isn't responsible on a shared platform. We have to test updates before we run them, or we risk the health of our entire platform. We tried to keep up at first, but by the time we'd finish testing the latest version of Core they would have released another version. So it's untenable for us. The .NET Core "slow development" version that we use, the one geared toward enterprise and platforms like ours - that version lags behind the latest bleeding edge version. By design. It's behind so they can ensure its stability. So that's where we're at with Core. We're sorry if we left you feeling like we promised something that we couldn't deliver. That's never our intention. But again, we do support Framework-dependent .NET Core on the web servers. Just not the very latest version(s).