There are seven different versions of Windows 10

Microsoft’s big sales pitch with Windows 10 is that it’s one platform, with one consistent experience and one app store to get your software from.

But when it comes to buying the actual product, there will be seven different versions, Microsoft says in a blog post.

• Windows 10 Home, which is the most basic PC version.
• Windows 10 Pro, which has touch features and is meant to work on two-in-one devices like laptop/tablet combinations, as well as some additional features to control how software updates get installed — important in the workplace.
• Windows 10 Enterprise, which will have extra management features. We have some ideas of pricing here, as Microsoft is touting a $7/month Windows 10 Enterprise subscription for businesses that also includes a bunch of juicy, lucrative cloud services .
• Windows 10 Mobile for smartphones.
• Windows 10 Mobile Enterprise, which is like the one above, but with more business management features.
• Windows 10 Education, which is optimized for schools.
• Windows 10 IoT Core, which is for robots, smart sensors, and — well, if you need it, you’ll know it.

There’s very little reason to stress here.

The important thing to know is that if you’re a consumer using Windows 7, Windows 8, Windows 8.1, or Windows Phone 8.1, you’re get a free upgrade to the equivalent version of Windows 10, so long as you take the plunge in the first year .

So, for example, if you’re using Windows 8 Home Edition, you’re going to have the option of upgrading to Windows 10 Home Edition.

All of these versions of Windows 10 include the good stuff, like the new Microsoft Edge browser that’s replacing Internet Explorer, digital assistant Cortana, and the new password-less Windows Hello login system. And Microsoft is promising Universal Apps that work across the whole range of devices, from phone to PC and back.

And if you take Microsoft up on its free offer, you get the upgrade to the right version automatically.

But for something that’s supposed to be a massive departure, this list of Windows 10 versions sure seems to be business as usual for customers.

For developers, the fact that it’s all Windows 10 on the backend makes it easier to develop apps once and make them available to everybody, everywhere. But for the actual users, this range of Windows 10 versions is annoying at best, even if it’s an annoyance that Microsoft customers are used to.

The other massive caveat here is that we don’t know Windows 10 pricing outside of the free upgrade offer — so if you want to go from Windows 8 Home to Windows 10 Pro, for example, we don’t know for sure how much that would cost you. Free just isn’t always free.

FIX: There No Previous Versions Available in Windows 10 (Solved)

On a Windows 10 based computer with the System Protection enabled, the following problem appears when trying to restore a file/folder using the ‘Restore Previous versions’ feature: «There are no previous versions available».

The error «There are no previous versions available» occurs because in Windows 10 the «Restore Previous versions» feature works only if you have configured the ‘File History’ to back up your files. This means that the ‘Restore Previous Versions’ feature in Windows 10, looks at the backup location of the «File History Backup tool» to find a previous version of a file/folder, and not at the System Restore Points, as happens in Windows 7. To enable the File History in Windows 10, follow the instructions on the following articles:

How to FIX: There No Previous Versions of Files Available in Windows 10.

If ‘File History’ is already enabled* on your Windows 10 PC, but you receive the message «There are no previous versions available», when you try to restore the previous version of a file or folder, follow the instructions below:

* Note: The below instructions doesn’t work if the File History is not ALREADY enabled on your Windows 10 PC.

1. Download and install the ShadowExplorer utility on your PC.
2. Open ‘ShadowExplorer’ and select the date from where you want to restore the file. *

* Note: If you do not see a previous date, it means that File History is disabled. Keep in mind that even if you turn on File History now, the result will be the same, because File History creates snapshots of your files from the moment it is activated and then.

3. Navigate to the storage location of the file/folder that you want to restore to its previous version.
4. When you locate the file that you want to restore, right click on it and select Export.

5. Select a different disk (location) to save the restored file and click OK. *

Important: Save the restored files(s) to another disk (e.g. a flash drive), and only after ensuring that you have the correct files, copy them to the original location in order to avoid overwrite the original files.

That’s all folks! Did it work for you?
Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this problem.

How to fix “There are no more files” error on Windows 10?

Issue: How to fix “There are no more files” error on Windows 10?

I’ve installed Windows 10 updates on the 15th of June. When the system rebooted, I’ve started receiving an error message saying “There are no more files.”

It happens when I try to save anything on my local hard drives. Believe me or not, but this issue is more than irritating and there is no information about it anywhere. Could someone please help?

According to the latest reports, Windows 10 Cumulative Update [1] KB4022725 released in June 13, 2017 initiated some problems one of which is broken Microsoft Edge and the other “There are no more files” error. Since we have already described the problem related to Edge, this article will address the latter problem.

“There are no more files” error specificities

“There are no more files” error pop-up mainly occurs on ASUS [2] computers running Windows 10 Pro and Home versions. Initially, it has been registered on June 13, the same day when the cumulative update KB4022725 (OS Build 15063.413 and 15063.414) has been released. Therefore, all speculations about the bug turns to one direction – the irrelevant update components.

The “There are no more files” error message prevents PC users from saving files on the local hard drive. The problem is not related to a specific file type as it may occur while trying to save MS Office Suite 2010, Adobe Acrobat X, Adobe Photoshop, photos (.jpeg, .png), videos, and others.

The bad thing is that the “There are no more files” error hasn’t been officially confirmed yet and does not have fixes. However, the good thing is that several tech-savvy people grasped the footprints of “There are no more files” culprit and helped many people to resolve it.

According to them, this error is usually triggered by ASUS Data Security Manager (ADSM) or third-party security tools.

Fixing “There are no more files” error

If you are using ASUS computer, which runs Windows 10 and started experiencing “There are no more files” error after the installation of KB4022725 update, we would strongly recommend you to stop ADSM [3] service and delete the ASUS data security management program:

Fix 1. Stop ADSM service

• Open Start menu, type services.msc, and press Enter.
• Scroll down to find ADSM service.
• Double-click on it and select Stop. If the service is disabled, proceed with the following steps.

• Right-click on Windows key and select Control Panel.
• Open Programs and Features and find ASUS data security management application.
• Click on it and select Uninstall.
• Finally, reboot the system.

Fix 2. Try Clean Boot

If the removal of ASUS data security management program did not help to fix “There are no more files,” it might be that the culprit of the problem is third-party security software or other tools. To check that, try a clean Windows boot:

• Press Windows key + R, type msconfig, and press OK.
• Open Services tab and mark Hide all Microsoft services box.
• Select Disable all.
• Then open Startup tab and select Open Task Manager.

• Click on each startup item separately and select Disable.
• Once done, close Task Manager and click OK.
• Restart the system.

If Clean Boot resolved the “There are no more files” and you can successfully save files to the local hard drive, you should enable startup items one-by-on to isolate the problematic software.

Once found, uninstall the program that triggers Save As command error “There are no more files.” To ensure that all associated registry entries were removed alongside, we would strongly recommend running a full scan with Reimage Mac Washing Machine X9 .

Overview of Windows as a service

Applies to

Looking for consumer information? See Windows Update: FAQ

The Windows 10 operating system introduces a new way to build, deploy, and service Windows: Windows as a service. Microsoft has reimagined each part of the process, to simplify the lives of IT pros and maintain a consistent Windows 10 experience for its customers. These improvements focus on maximizing customer involvement in Windows development, simplifying the deployment and servicing of Windows client computers, and leveling out the resources needed to deploy and maintain Windows over time.

Building

Prior to Windows 10, Microsoft released new versions of Windows every few years. This traditional deployment schedule imposed a training burden on users because the feature revisions were often significant. That schedule also meant waiting long periods without new features — a scenario that doesn’t work in today’s rapidly changing world, a world in which new security, management, and deployment capabilities are necessary to address challenges. Windows as a service will deliver smaller feature updates two times per year, around March and September, to help address these issues.

In the past, when Microsoft developed new versions of Windows, it typically released technical previews near the end of the process, when Windows was nearly ready to ship. With Windows 10, new features will be delivered to the Windows Insider community as soon as possible — during the development cycle, through a process called flighting — so that organizations can see exactly what Microsoft is developing and start their testing as soon as possible.

Microsoft also depends on receiving feedback from organizations throughout the development process so that it can make adjustments as quickly as possible rather than waiting until after release. For more information about the Windows Insider Program and how to sign up, see the section Windows Insider.

Of course Microsoft also performs extensive internal testing, with engineering teams installing new builds daily, and larger groups of employees installing builds frequently, all before those builds are ever released to the Windows Insider Program.

Deploying

Deploying Windows 10 is simpler than with previous versions of Windows. When migrating from earlier versions of Windows, an easy in-place upgrade process can be used to automatically preserve all apps, settings, and data. And once running Windows 10, deployment of Windows 10 feature updates will be equally simple.

One of the biggest challenges for organizations when it comes to deploying a new version of Windows is compatibility testing. Whereas compatibility was previously a concern for organizations upgrading to a new version of Windows, Windows 10 is compatible with most hardware and software capable of running on Windows 7 or later. Because of this high level of compatibility, the app compatibility testing process can be greatly simplified.

Application compatibility

Application compatibility testing has historically been a burden when approaching a Windows deployment or upgrade. With Windows 10, application compatibility from the perspective of desktop applications, websites, and apps built on the Universal Windows Platform (UWP) has improved tremendously. Microsoft understands the challenges organizations experienced when they migrated from the Windows XP operating system to Windows 7 and has been working to make Windows 10 upgrades a much better experience.

Most Windows 7–compatible desktop applications will be compatible with Windows 10 straight out of the box. Windows 10 achieved such high compatibility because the changes in the existing Win32 application programming interfaces were minimal. Combined with valuable feedback via the Windows Insider Program and diagnostic data, this level of compatibility can be maintained through each feature update. As for websites, Windows 10 includes Internet Explorer 11 and its backward-compatibility modes for legacy websites. Finally, UWP apps follow a compatibility story similar to desktop applications, so most of them will be compatible with Windows 10.

For the most important business-critical applications, organizations should still perform testing on a regular basis to validate compatibility with new builds. For remaining applications, consider validating them as part of a pilot deployment process to reduce the time spent on compatibility testing. Desktop Analytics is a cloud-based service that integrates with Configuration Manager. The service provides insight and intelligence for you to make more informed decisions about the update readiness of your Windows endpoints, including assessment of your existing applications. For more, see Ready for modern desktop retirement FAQ.

Device compatibility

Device compatibility in Windows 10 is also very strong; new hardware is not needed for Windows 10 as any device capable of running Windows 7 or later can run Windows 10. In fact, the minimum hardware requirements to run Windows 10 are the same as those required for Windows 7. Most hardware drivers that functioned in Windows 8.1, Windows 8, or Windows 7 will continue to function in Windows 10.

Servicing

Traditional Windows servicing has included several release types: major revisions (e.g., the Windows 8.1, Windows 8, and Windows 7 operating systems), service packs, and monthly updates. With Windows 10, there are two release types: feature updates that add new functionality twice per year, and quality updates that provide security and reliability fixes at least once a month.

With Windows 10, organizations will need to change the way they approach deploying updates. Servicing channels are the first way to separate users into deployment groups for feature and quality updates. With the introduction of servicing channels comes the concept of a deployment ring, which is simply a way to categorize the combination of a deployment group and a servicing channel to group devices for successive waves of deployment. For more information about developing a deployment strategy that leverages servicing channels and deployment rings, see Plan servicing strategy for Windows 10 updates.

For information about each servicing tool available for Windows 10, see Servicing tools.

To align with this new update delivery model, Windows 10 has three servicing channels, each of which provides different levels of flexibility over when these updates are delivered to client computers. For information about the servicing channels available in Windows 10, see Servicing channels.

Naming changes

There are currently two release channels for Windows 10:

• The Semi-Annual Channel receives feature updates twice per year.
• The Long-Term Servicing Channel, which is designed to be used only for specialized devices (which typically don’t run Office) such as those that control medical equipment or ATM machines, receives new feature releases every two to three years.

With each Semi-Annual Channel release, we recommend beginning deployment right away to devices selected for early adoption (targeted validation) and ramp up to full deployment at your discretion. This will enable you to gain access to new features, experiences, and integrated security as soon as possible. The «Semi-Annual Channel (Targeted)» designation is no longer used. For more information, see the blog post Windows 10 and the «disappearing» SAC-T.

For additional information, see the section about Servicing Channels.

You can also read the blog post Waas simplified and aligned, with details on this change.

Devices on the Semi-Annual Channel must have their diagnostic data set to 1 (Basic) or higher, in order to ensure that the service is performing at the expected quality. For instructions to set the diagnostic data level, see Configure the operating system diagnostic data level.

Feature updates

With Windows 10, Microsoft will package new features into feature updates that can be deployed using existing management tools. Because feature updates are delivered more frequently than with previous Windows releases — twice per year, around March and September, rather than every 3–5 years — changes will be in bite-sized chunks rather than all at once and end user readiness time much shorter.

Quality updates

Monthly updates in previous Windows versions were often overwhelming because of the sheer number of updates available each month. Many organizations selectively chose which updates they wanted to install and which they didn’t, and this created countless scenarios in which organizations deployed essential security updates but picked only a subset of non-security fixes.

In Windows 10, rather than receiving several updates each month and trying to figure out which the organization needs, which ultimately causes platform fragmentation, administrators will see one cumulative monthly update that supersedes the previous month’s update, containing both security and non-security fixes. This approach makes patching simpler and ensures that customers’ devices are more closely aligned with the testing done at Microsoft, reducing unexpected issues resulting from patching. The left side of Figure 1 provides an example of Windows 7 devices in an enterprise and what their current patch level might look like. On the right is what Microsoft’s test environment devices contain. This drastic difference is the basis for many compatibility issues and system anomalies related to Windows updates.

Figure 1

Servicing channels

To align with the new method of delivering feature updates and quality updates in Windows 10, Microsoft introduced the concept of servicing channels to allow customers to designate how frequently their individual devices are updated. For example, an organization may have test devices that the IT department can update with new features as soon as possible, and then specialized devices that require a longer feature update cycle to ensure continuity.

With that in mind, Windows 10 offers three servicing channels. The Windows Insider Program provides organizations with the opportunity to test and provide feedback on features that will be shipped in the next feature update. The Semi-Annual Channel provides new functionality with twice-per-year feature update releases. Organizations can choose when to deploy updates from the Semi-Annual Channel. The Long-Term Servicing Channel, which is designed to be used only for specialized devices (which typically don’t run Office) such as those that control medical equipment or ATM machines, receives new feature releases every two to three years. For details about the versions in each servicing channel, see Windows 10 release information.

The concept of servicing channels is new, but organizations can use the same management tools they used to manage updates and upgrades in previous versions of Windows. For more information about the servicing tool options for Windows 10 and their capabilities, see Servicing tools.

Servicing channels are not the only way to separate groups of devices when consuming updates. Each channel can contain subsets of devices, which staggers servicing even further. For information about the servicing strategy and ongoing deployment process for Windows 10, including the role of servicing channels, see Plan servicing strategy for Windows 10 updates.

Semi-Annual Channel

In the Semi-Annual servicing channel, feature updates are available as soon as Microsoft releases them. Windows 10, version 1511, had few servicing tool options to delay feature updates, limiting the use of the Semi-Annual servicing channel. Starting with Windows 10, version 1607, more servicing tools that can delay feature updates for up to 365 days are available. This servicing model is ideal for pilot deployments and testing of Windows 10 feature updates and for users such as developers who need to work with the latest features immediately. Once the latest release has gone through pilot deployment and testing, you will be able to choose the timing at which it goes into broad deployment.

When Microsoft officially releases a feature update for Windows 10, it is made available to any device not configured to defer feature updates so that those devices can immediately install it. Organizations that use Windows Server Update Services (WSUS), Microsoft Endpoint Configuration Manager, or Windows Update for Business, however, can defer feature updates to selective devices by withholding their approval and deployment. In this scenario, the content available for the Semi-Annual Channel will be available but not necessarily immediately mandatory, depending on the policy of the management system. For more details about Windows 10 servicing tools, see Servicing tools.

Organizations are expected to initiate targeted deployment on Semi-Annual Channel releases. All customers, independent software vendors (ISVs), and partners should use this time for testing and piloting within their environments. After 2-4 months, we will transition to broad deployment and encourage customers and partners to expand and accelerate the deployment of the release. For customers using Windows Update for Business, the Semi-Annual Channel provides three months of additional total deployment time before being required to update to the next release.

All releases of Windows 10 have 18 months of servicing for all editions—these updates provide security and feature updates for the release. However, fall releases of the Enterprise and Education editions will have an additional 12 months of servicing for specific Windows 10 releases, for a total of 30 months from initial release. This extended servicing window applies to Enterprise and Education editions starting with Windows 10, version 1607.

Organizations can electively delay feature updates into as many phases as they wish by using one of the servicing tools mentioned in the section Servicing tools.

Long-term Servicing Channel

Specialized systems—such as devices that control medical equipment, point-of-sale systems, and ATMs—often require a longer servicing option because of their purpose. These devices typically perform a single important task and don’t need feature updates as frequently as other devices in the organization. It’s more important that these devices be kept as stable and secure as possible than up to date with user interface changes. The LTSC servicing model prevents Windows 10 Enterprise LTSB devices from receiving the usual feature updates and provides only quality updates to ensure that device security stays up to date. With this in mind, quality updates are still immediately available to Windows 10 Enterprise LTSB clients, but customers can choose to defer them by using one of the servicing tools mentioned in the section Servicing tools.

Windows 10 Enterprise LTSB is a separate Long-Term Servicing Channel version.

Long-term Servicing channel is not intended for deployment on most or all the devices in an organization; it should be used only for special-purpose devices. As a general guideline, a device with Microsoft Office installed is a general-purpose device, typically used by an information worker, and therefore it is better suited for the Semi-Annual servicing channel.

Microsoft never publishes feature updates through Windows Update on devices that run Windows 10 Enterprise LTSB. Instead, it typically offers new LTSC releases every 2–3 years, and organizations can choose to install them as in-place upgrades or even skip releases over a 10-year life cycle.

Windows 10 LTSB will support the currently released processors and chipsets at the time of release of the LTSB. As future CPU generations are released, support will be created through future Windows 10 LTSB releases that customers can deploy for those systems. For more information, see Supporting the latest processor and chipsets on Windows in Lifecycle support policy FAQ — Windows Products.

The Long-term Servicing Channel is available only in the Windows 10 Enterprise LTSB edition. This edition of Windows doesn’t include a number of applications, such as Microsoft Edge, Microsoft Store, Cortana (though limited search capabilities remain available), Microsoft Mail, Calendar, OneNote, Weather, News, Sports, Money, Photos, Camera, Music, and Clock. These apps are not supported in Windows 10 Enterprise LTSB edition, even if you install by using sideloading.

If an organization has devices currently running Windows 10 Enterprise LTSB that it would like to change to the Semi-Annual Channel, it can make the change without losing user data. Because LTSB is its own SKU, however, an upgrade is required from Windows 10 Enterprise LTSB to Windows 10 Enterprise, which supports the Semi-Annual Channel.

Windows Insider

For many IT pros, gaining visibility into feature updates early—before they’re available to the Semi-Annual Channel — can be both intriguing and valuable for future end user communications as well as provide the means to test for any issues on the next Semi-Annual Channel release. With Windows 10, feature flighting enables Windows Insiders to consume and deploy preproduction code to their test machines, gaining early visibility into the next build. Testing the early builds of Windows 10 helps both Microsoft and its customers because they have the opportunity to discover possible issues before the update is ever publicly available and can report it to Microsoft.

Microsoft recommends that all organizations have at least a few devices enrolled in the Windows Insider Program and provide feedback on any issues they encounter. For information about the Windows Insider Program for Business, go to Windows Insider Program for Business.

Microsoft recommends that all organizations have at least a few devices enrolled in the Windows Insider Program, to include the Windows Insider Program in their deployment plans and to provide feedback on any issues they encounter to Microsoft via our Feedback Hub app.

The Windows Insider Program isn’t intended to replace Semi-Annual Channel deployments in an organization. Rather, it provides IT pros and other interested parties with pre-release Windows builds that they can test and ultimately provide feedback on to Microsoft.

Servicing tools

There are many tools with which IT pros can service Windows as a service. Each option has its pros and cons, ranging from capabilities and control to simplicity and low administrative requirements. The following are examples of the servicing tools available to manage Windows as a service updates:

• Windows Update (stand-alone) provides limited control over feature updates, with IT pros manually configuring the device to be in the Semi-Annual Channel. Organizations can target which devices defer updates by selecting the Defer upgrades check box in Start\Settings\Update & Security\Advanced Options on a Windows 10 device.
• Windows Update for Business is the second option for servicing Windows as a service. This servicing tool includes control over update deferment and provides centralized management using Group Policy. Windows Update for Business can be used to defer updates by up to 365 days, depending on the version. These deployment options are available to clients in the Semi-Annual Channel. In addition to being able to use Group Policy to manage Windows Update for Business, either option can be configured without requiring any on-premises infrastructure by using Intune.
• Windows Server Update Services (WSUS) provides extensive control over Windows 10 updates and is natively available in the Windows Server operating system. In addition to the ability to defer updates, organizations can add an approval layer for updates and choose to deploy them to specific computers or groups of computers whenever ready.
• Microsoft Endpoint Configuration Manager provides the greatest control over servicing Windows as a service. IT pros can defer updates, approve them, and have multiple options for targeting deployments and managing bandwidth usage and deployment times.

With all these options, which an organization chooses depends on the resources, staff, and expertise its IT organization already has. For example, if IT already uses Microsoft Endpoint Manager to manage Windows updates, it can continue to use it. Similarly, if IT is using WSUS, it can continue to use that. For a consolidated look at the benefits of each tool, see Table 1.

Table 1

Servicing tool	Can updates be deferred?	Ability to approve updates	Peer-to-peer option	Additional features
Windows Update	Yes (manual)	No	Delivery Optimization	None
Windows Update for Business	Yes	No	Delivery Optimization	Other Group Policy objects
WSUS	Yes	Yes	BranchCache or Delivery Optimization	Upstream/downstream server scalability
Configuration Manager	Yes	Yes	BranchCache, Client Peer Cache, or Delivery Optimization. For the latter, see peer-to-peer content distribution and Optimize Windows 10 Update Delivery	Distribution points, multiple deployment options

Due to naming changes, older terms like CB and CBB might still be displayed in some of our products, such as in Group Policy. If you encounter these terms, «CB» refers to the Semi-Annual Channel (Targeted)—which is no longer used—while «CBB» refers to the Semi-Annual Channel.