After windows 10 update, how do I remove the Windows.old folder?

Folder ‘$Windows.~bt’ contains the temporary windows installation files

After upgrading to windows 10, a copy of old OS is retained in the folder Windows.old. If everything is working fine and you don’t want to revert to old OS, you can remove its content to make more free space. But just deleting the Windows.old directory won’t let you remove the files in it as most of them are considered as system files.

To delete the Windows.old folder, please follow these steps.

> In ‘Search the web and windows’ box, type ‘Free up disk space’
> Click the option ‘Free up disk space by deleting unnecessary files’
> Select the drive in which windows is installed and click OK.
> Click ‘Clean up system files’
> ‘Disk Clean up: Drive Selection’ window appear again, make sure the correct drive is selected and click OK.
> Check the option ‘Previous Windows Installation(s) and click OK.
> Folder ‘$Windows.~bt’ contains the temporary windows installation files and it can be deleted as well, Check the option ‘Temporary Windows Installation Files’
> Click ‘Delete Files’ and ‘Yes’ to confirm your decision.

That’s all. It can take few minutes to delete the files.

One Rupee Hosting + Free domain

Get 1Gb cPanel shared hosting and Free .com or .IN domain for just Rs 1024 per year.

  • Disk Space 1Gb
  • Bandwidth 10Gb
  • Website allowed 1
  • Email Accounts 250
  • Databases 250

Free domain valid for first year only.

Please feel free to contact our customer service department for more details.

We’re celebrating 6 great years of Hosting Business

A grand 6th year for Zaveo Technologies, we have no one else to thank other than our customers! A heartfelt thank you from the entire team, without you this would not have been possible.

With a humble beginning way back in 2008, Zaveo Technologies has emerged over the years into one of the most known brands in this segment. We had a slow yet steady growth, and for this we are grateful to our customers who trusted every step we took and stayed with us.  Our clientele ranging from 6 year old customers are our absolute assets.

During this tenure, rather say for the past one year we had major changes and steps in the business. We have our own servers now expanding over to 3 data centres. Server migration, IP changes, well yes it was a busy time. Our clients completely understood during this transfer phase, for that  we now have servers in US, UK and Singapore Data centres. We implemented a new Billing System, adding up online payment methods for all our customers which were highly appreciated.

Defining the next year our short term goals would be an expansion over to Dubai Data centre (by 2014 end), a complete website revamping and integration of new billing system, adding more exciting features. On long term goals our vision is our own DC by 2020!  We know, and we look forward to the complete support from all our customers, we are here just because of you. We believe that we would receive continual support by our customers on all future endeavours.  Thank you for choosing Zaveo Technologies and thank you for referring us over your acquaintances.

We wish you all success in life and business, Zaveo Technologies are dedicated completely towards complete customer satisfaction.

OpenSSL Heartbleed Bug and how to handle this on cpanel servers

The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. More details can be found in

Only CentOS 6.5 is vulnerable to this bug. If you use a version of CentOS older than 6.5, you’re not affected.

You can test whether you’re vulnerable by using tool against a website on your server that has an SSL certificate installed.

A fix is not available yet  (at the time of writing) but it is possible to disable the TLS heartbeat extensions that are vulnerable by following these steps.

Login to WHM > Server Configuration > Update Preference > Set ‘Operating System Package Updates’ Automatic and run cpanel update.

Make sure to restart all services or restart the entire server. Check your SSL installed url again.

All good, seems safe! 🙂