What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use Intune’s Allow full screen mode setting in a Windows device-restrictions profile. Choose Yes to let Microsoft Edge users, permitted apps, and extensions enter full-screen mode; choose No to block them. The corresponding Edge browser policy is FullscreenAllowed. A critical kiosk caveat applies: disabling this policy also prevents launching Edge kiosk mode from the command line, so test signage and kiosk deployments before blocking fullscreen.
What the Intune setting controls
Edge full-screen mode removes the browser’s visible interface and leaves the web page as the primary on-screen content. The Intune setting controls whether Edge is allowed to enter that state. It is a browser capability switch, not a complete configuration for turning a Windows computer into a kiosk.
As an Amazon Associate I earn from qualifying purchases.
Microsoft documents the policy as a mandatory Boolean policy named FullscreenAllowed, with the friendly setting name Allow full screen mode. The policy is documented for Windows devices running Microsoft Edge 77 or later. It is not supported by this policy reference on macOS, Android, or iOS.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChoose the correct value
| Intune value | Browser policy state | Effect on Edge | Kiosk consideration |
|---|---|---|---|
| Yes | Enabled | Users, apps, and extensions with the required permissions can enter full-screen mode. | Does not by itself create a kiosk. It preserves the fullscreen permission needed by many signage scenarios. |
| No | Disabled | Users, apps, and extensions cannot enter full-screen mode. | Command-line launching of Edge in kiosk mode is unavailable when this policy is disabled. |
| Not configured | Policy not enforced by this profile | Edge follows its normal behavior and other applicable management settings. | Do not assume that leaving the setting blank is equivalent to an intentional kiosk configuration. |
Use No when preventing presentation-style browser takeover is the requirement. Use Yes when a managed application, training display, or signage workflow must be able to show content without Edge’s toolbar and tabs. If you are unsure, separate the general user population from kiosk devices and assign different profiles rather than applying one compromise value to every device.
#1 Best Overall
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
How to configure it in Microsoft Intune
Intune’s admin-center labels can change as Microsoft updates the service. The reliable configuration sequence is to use a Windows device-restrictions profile, search for the documented setting name, assign the profile, and then verify receipt on representative devices.
- Create or edit a Windows device-restrictions profile. Select the Windows platform and the device-restrictions profile type used by your tenant. If an existing profile already governs Edge behavior, edit that profile only after checking its current assignments and other settings.
- Find the setting. Search the profile settings for Allow full screen mode. Do not search only for the internal policy name; Intune normally presents the friendly name while Microsoft’s Edge policy documentation calls the setting
FullscreenAllowed. - Select the value. Set it to Yes to permit fullscreen or No to prevent it. Treat this as a device policy decision: the setting affects Edge behavior for the users, apps, and extensions operating on the assigned Windows device.
- Save the profile and assign it. Target the user or device groups that should receive the policy. Keep kiosk devices in a clearly identified assignment group so that a general-purpose restriction does not unintentionally disable their browser launch method.
- Check deployment status. Use Intune’s per-setting and device assignment reporting to confirm that the intended devices received the profile. The Edge policy supports dynamic policy refresh, but Microsoft does not promise one universal delivery time for every device. A successful assignment in the portal is not proof that every endpoint has already processed it.
- Validate behavior on a managed device. With the policy set to Yes, confirm that an approved web experience can enter fullscreen. With No, confirm that the same action is blocked. Test with the actual account, application, and extension combination used in production, because their permissions can affect whether fullscreen is available when the policy allows it.
Do not hand-edit the registry as a substitute for Intune management. Microsoft lists the policy-reference location as SOFTWARE\Policies\Microsoft\Edge, with a REG_DWORD value named FullscreenAllowed. Those details are useful when diagnosing a conventionally managed Windows device or reconciling Group Policy documentation; an Intune administrator should configure the corresponding device restriction instead of creating a competing local setting.
Understand the difference between fullscreen permission and kiosk mode
A fullscreen permission answers one question: may Edge hide its interface and show web content? Kiosk mode answers a broader device-management question: how should Windows launch and constrain the browser for a dedicated task? A kiosk profile controls the device’s kiosk experience, while Edge-specific browser settings are configured separately. Microsoft’s Intune guidance says those profiles should be assigned to the same devices.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11For a single-app, full-screen Windows kiosk running Edge, create the Windows kiosk configuration and then configure the Edge settings required by the site. Do not assume that setting Allow full screen mode automatically creates the account, shell, app assignment, navigation restrictions, or other controls expected of a kiosk.
Rank #2
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Edge kiosk experiences and their fullscreen implications
| Edge kiosk experience | Typical purpose | Browser behavior documented by Microsoft | Policy planning point |
|---|---|---|---|
| Digital/Interactive Signage | Displaying a specific website or web experience on a dedicated screen. | Designed to show a selected site full screen. The cited kiosk guidance describes it as running in InPrivate mode. | Keep Allow full screen mode enabled unless you have verified an alternative launch design that does not depend on the permission. |
| Public Browsing | Providing a restricted browsing station rather than a single fixed page. | Offers a limited multi-tab experience and runs in InPrivate mode under the documented kiosk configuration. | Test navigation, tab behavior, and any additional Edge policies together; fullscreen permission alone does not define the browsing restrictions. |
The Edge kiosk documentation applies to Edge 87 or later and describes these experiences as available in the Stable Channel. Intune’s Windows kiosk guidance likewise identifies Edge 87 or later for the current browser option. That is a different minimum from the general FullscreenAllowed policy, which is documented from Edge 77 onward.
The command-line kiosk caveat
Microsoft explicitly states that disabling FullscreenAllowed makes launching Edge in kiosk mode from the command line unavailable. This is why a blanket “No” assignment can break an otherwise valid signage deployment. The failure is not limited to a user pressing a fullscreen control; the policy changes whether the kiosk launch path is available.
Before assigning No to devices used for signage or public access, test the complete sequence: device sign-in, kiosk account activation, Edge launch, site loading, fullscreen presentation, and recovery after a restart or sign-out. If the kiosk cannot launch after the policy is applied, set the policy to Yes for that device group and investigate other restrictions separately.
Free tools Windows power users keep installed
One-click scans. No signup required.
Microsoft also cautions that additional Edge policies can negatively affect kiosk functionality. Add restrictions one at a time in a pilot group, record the intended result, and confirm that the kiosk still starts and displays its assigned content before expanding the assignment.
Rank #3
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
Which devices and versions are in scope?
- Operating system: The documented
FullscreenAllowedpolicy is for Windows. The reference marks it unsupported on macOS, Android, and iOS. - General Edge policy: Microsoft documents support from Edge version 77.
- Edge kiosk option: The cited kiosk documentation applies to Edge 87 or later and identifies Stable Channel availability for the described kiosk mode.
- Windows lifecycle: Microsoft’s Intune kiosk reference records October 14, 2025 as the end-of-support date for Windows 10. Windows 10 may still appear as an allowed Intune version, but eligible functionality is not guaranteed and can vary. Check your organization’s current operating-system support policy before relying on Windows 10 kiosk behavior.
These version boundaries matter when a profile appears correctly assigned but behaves differently across device groups. Compare the Edge version, Windows edition and support status, and whether the device is actually using the kiosk configuration you intended.
Verification checklist after assignment
- Confirm the device is in the intended Intune assignment group and is not excluded by a filter or conflicting profile.
- Check the profile’s per-device status rather than relying only on the profile’s overall assignment state.
- Verify that the endpoint runs Windows and a supported Edge version.
- Test with the same user account, managed app, and extension set used in production.
- For a kiosk, verify both the Windows kiosk profile and the separate Edge browser settings profile target the same device.
- Record whether the device received the policy before judging the browser result; dynamic refresh is supported, but delivery timing is not universal.
Troubleshoot common outcomes
Fullscreen remains available after setting No
First establish that the device processed the profile. Review assignment and per-setting status, then check for an excluded group or a second management profile addressing the same device. Confirm that you changed Allow full screen mode, not an unrelated Edge restriction. If the policy has not reached the endpoint, browser behavior cannot yet demonstrate whether the setting works.
Fullscreen is blocked after setting Yes
Check the Edge version and operating system against the policy scope. Then test the actual site and account: the policy permits entry, but an app or extension still needs appropriate permissions. A site can also implement its own display behavior that is different from the browser’s full-screen API. Keep the policy result separate from site-specific functionality when diagnosing the issue.
Recommended Free Tools
Edge kiosk no longer launches
Review whether FullscreenAllowed was set to No on that device. Microsoft identifies command-line kiosk launch as unavailable when the policy is disabled. Restore Yes for the kiosk assignment, retest the launch path, and then introduce other restrictions individually so the responsible setting is clear.
Rank #4
- Video Link to instructions and Free support VIA Amazon
- 24/7 Tech Support!
- key code included
A kiosk launches but does not behave as expected
Confirm that the Windows kiosk profile and Edge-specific settings are separate profiles assigned to the same devices. Check the Edge version requirement for the selected kiosk experience. Finally, remove or pilot additional Edge policies one at a time; a policy intended for ordinary desktops can interfere with kiosk startup, navigation, or presentation.
Practical policy decisions
Managed desktops and laptops
If the goal is to stop users from hiding browser controls during ordinary work, assign No to the appropriate Windows device group and verify that no business application depends on fullscreen. If the organization merely wants to permit fullscreen for presentations or web applications, assign Yes and leave kiosk configuration out of the decision.
Dedicated signage
Use a Windows kiosk profile for the device, configure the Edge signage experience separately, and normally keep Allow full screen mode at Yes. Validate the exact launch method used by the kiosk before broad deployment because the disabled state removes command-line kiosk launching.
Public browsing stations
Choose the Public Browsing kiosk experience when a limited multi-tab InPrivate workflow is required. Treat fullscreen permission, tab limits, navigation controls, and other Edge restrictions as separate settings. Pilot the complete combination on the same Edge and Windows versions that will be installed in production.
Quick Recap
Key takeaways
- Search Intune for Allow full screen mode; the Edge policy name is
FullscreenAllowed. - Yes permits fullscreen; No blocks users, apps, and extensions from entering it.
- The policy is documented for Windows and Edge 77 or later, not macOS, Android, or iOS.
- Edge kiosk mode is a separate Windows device configuration. Digital/Interactive Signage and Public Browsing have different purposes and are documented for Edge 87 or later.
- Disabling fullscreen also disables command-line launching of Edge kiosk mode, so test that dependency before assigning No to kiosk devices.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
