windows-itpro-docs/windows/security/information-protection/windows-information-protection/limitations-with-wip.md

title, description, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, author, ms.author, manager, audience, ms.collection, ms.topic, ms.date, ms.localizationpriority

title	description	keywords	ms.prod	ms.mktglfcycl	ms.sitesec	ms.pagetype	author	ms.author	manager	audience	ms.collection	ms.topic	ms.date	ms.localizationpriority
Limitations while using Windows Information Protection (WIP) (Windows 10)	This section includes info about the common problems you might encounter while using Windows Information Protection (WIP).	WIP, Windows Information Protection, EDP, Enterprise Data Protection	w10	explore	library	security	justinha	justinha	dansimp	ITPro	M365-security-compliance	conceptual	04/05/2019	medium

Limitations while using Windows Information Protection (WIP)

Applies to:

• Windows 10, version 1607 and later
• Windows 10 Mobile, version 1607 and later

This table provides info about the most common problems you might encounter while running WIP in your organization.

Limitation	How it appears	Workaround
Your enterprise data on USB drives might be tied to the device it was protected on, based on your Azure RMS configuration.	If you’re using Azure RMS: Authenticated users can open enterprise data on USB drives, on computers running Windows 10, version 1703. If you’re not using Azure RMS: Data in the new location remains encrypted, but becomes inaccessible on other devices and for other users. For example, the file won't open or the file opens, but doesn't contain readable text.	Share files with fellow employees through enterprise file servers or enterprise cloud locations. If data must be shared via USB, employees can decrypt protected files, but it will be audited. We strongly recommend educating employees about how to limit or eliminate the need for this decryption.
Direct Access is incompatible with WIP.	Direct Access might experience problems with how WIP enforces app behavior and data movement because of how WIP determines what is and isn’t a corporate network resource.	We recommend that you use VPN for client access to your intranet resources. Note VPN is optional and isn’t required by WIP.
NetworkIsolation Group Policy setting takes precedence over MDM Policy settings.	The NetworkIsolation Group Policy setting can configure network settings that can also be configured by using MDM. WIP relies on these policies being correctly configured.	If you use both Group Policy and MDM to configure your NetworkIsolation settings, you must make sure that those same settings are deployed to your organization using both Group Policy and MDM.
Cortana can potentially allow data leakage if it’s on the allowed apps list.	If Cortana is on the allowed list, some files might become unexpectedly encrypted after an employee performs a search using Cortana. Your employees will still be able to use Cortana to search and provide results on enterprise documents and locations, but results might be sent to Microsoft.	We don’t recommend adding Cortana to your allowed apps list. However, if you wish to use Cortana and don't mind whether the results potentially go to Microsoft, you can make Cortana an Exempt app.
WIP is designed for use by a single user per device.	A secondary user on a device might experience app compat issues when unenlightened apps start to automatically encrypt for all users. Additionally, only the initial, enrolled user’s content can be revoked during the unenrollment process.	We recommend only having one user per managed device.
Installers copied from an enterprise network file share might not work properly.	An app might fail to properly install because it can’t read a necessary configuration or data file, such as a .cab or .xml file needed for installation, which was protected by the copy action.	To fix this, you can: Start the installer directly from the file share. -OR- Decrypt the locally copied files needed by the installer. -OR- Mark the file share with the installation media as “personal”. To do this, you’ll need to set the Enterprise IP ranges as Authoritative and then exclude the IP address of the file server, or you’ll need to put the file server on the Enterprise Proxy Server list.
Changing your primary Corporate Identity isn’t supported.	You might experience various instabilities, including but not limited to network and file access failures, and potentially granting incorrect access.	Turn off WIP for all devices before changing the primary Corporate Identity (first entry in the list), restarting, and finally redeploying.
Redirected folders with Client Side Caching are not compatible with WIP.	Apps might encounter access errors while attempting to read a cached, offline file.	Migrate to use another file synchronization method, such as Work Folders or OneDrive for Business. Note For more info about Work Folders and Offline Files, see the blog, [Work Folders and Offline Files support for Windows Information Protection](https://blogs.technet.microsoft.com/filecab/2016/08/29/work-folders-and-offline-files-support-for-windows-information-protection/). If you're having trouble opening files offline while using Offline Files and WIP, see the support article, [Can't open files offline when you use Offline Files and Windows Information Protection](https://support.microsoft.com/kb/3187045).
An unmanaged device can use Remote Desktop Protocol (RDP) to connect to a WIP-managed device.	Data copied from the WIP-managed device is marked as Work. Data copied to the WIP-managed device is not marked as Work. Local Work data copied to the WIP-managed device remains Work data. Work data that is copied between two apps in the same session remains data.	Disable RDP to prevent access because there is no way to restrict access to only devices managed by WIP. RDP is disabled by default.
You can't upload an enterprise file to a personal location using Microsoft Edge or Internet Explorer.	A message appears stating that the content is marked as Work and the user isn't given an option to override to Personal.	Open File Explorer and change the file ownership to Personal before you upload.
ActiveX controls should be used with caution.	Webpages that use ActiveX controls can potentially communicate with other outside processes that aren’t protected by using WIP.	We recommend that you switch to using Microsoft Edge, the more secure and safer browser that prevents the use of ActiveX controls. We also recommend that you limit the usage of Internet Explorer 11 to only those line-of-business apps that require legacy technology. For more info, see [Out-of-date ActiveX control blocking](https://technet.microsoft.com/itpro/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking).
Resilient File System (ReFS) isn't currently supported with WIP.	Trying to save or transfer WIP files to ReFS will fail.	Format drive for NTFS, or use a different drive.
WIP isn’t turned on if any of the following folders have the MakeFolderAvailableOfflineDisabled option set to False: AppDataRoaming Desktop StartMenu Documents Pictures Music Videos Favorites Contacts Downloads Links Searches SavedGames	WIP isn’t turned on for employees in your organization. Error code 0x807c0008 will result if WIP is deployed by using System Center Configuration Manager.	Don’t set the MakeFolderAvailableOfflineDisabled option to False for any of the specified folders. If you currently use redirected folders, we recommend that you migrate to a file synchronization solution that supports WIP, such as Work Folders or OneDrive for Business. Additionally, if you apply redirected folders after WIP is already in place, you might be unable to open your files offline. For more info about these potential access errors, see [Can't open files offline when you use Offline Files and Windows Information Protection](https://support.microsoft.com/help/3187045/can-t-open-files-offline-when-you-use-offline-files-and-windows-information-protection).
Only enlightened apps can be managed without device enrollment	If a user enrolls a device for Mobile Application Management (MAM) without device enrollment, only enlightened apps will be managed. This is by design to prevent personal files from being unintenionally encrypted by unenlighted apps. Unenlighted apps that need to access work using MAM need to be re-compiled as LOB apps or managed by using MDM with device enrollment.	If all apps need to be managed, enroll the device for MDM.
By design, files in the Windows directory (%windir% or C:/Windows) cannot be encrypted because they need to be accessed by any user. If a file in the Windows directory gets encypted by one user, other users can't access it.	Any attempt to encrypt a file in the Windows directory will return a file access denied error. But if you copy or drag and drop an encrypted file to the Windows directory, it will retain encryption to honor the intent of the owner.	If you need to save an encrypted file in the Windows directory, create and encrypt the file in a different directory and copy it.

Note

Help to make this topic better by providing us with edits, additions, and feedback. For info about how to contribute to this topic, see Contributing to our content.

Anywhere under c:windows* is a design. We don’t want you to shoot yourself in the foot. We don’t want that encrypted to a specific user because it’s used y all windows users. If you are logged in as one admin user and another user signs in as a diff admin user, they have no way to elevate to get the encrypted data.

If it’s in windir, they will not encrypt if it was already there. If there is a file in the dir and you try to encrypt it, it will fail. But if you drag and drop to there, it will retain encryption. That honors the intent of the owner. So if you redirect OneDrive to C:windows\temp, the files will not get encrypted. They won’t change it.

Put in the limitations section, add a section that says this is by design

Workaround,