IMDTouchKnowledge BaseShop main store

How-to

Managing UWF on Windows 10 IoT HMI panels

HMI and touchscreens Published 6 min read

Short answer

Windows 10 IoT HMIs use UWF, not the EWF your Windows 7 Embedded workflow relied on, and no documented behavior promises that a project download toggles the filter. Toggle UWF explicitly with the panel's documented procedure, prove each download by restarting and confirming the project still runs, and keep the filter on in production.

On this page
  1. EWF to UWF: what changed on Windows 10 IoT
  2. What the filter state does to a project download
  3. The two deployment cases
  4. The download-and-restart test
  5. Accept the workflow on this evidence
  6. Overlay headroom while the filter runs
  7. The decision, case by case
  8. Questions asked

On a Windows 10 IoT HMI, the write filter is yours to manage. The Unified Write Filter (UWF) that replaced EWF on Windows 7 Embedded panels has no documented link to the project download, so a transfer that reports success can still vanish at the next restart. Toggle UWF yourself with the panel's documented procedure, prove every download with a restart-and-persist check, and leave the filter on for normal running. That decision holds for the vendor's own Windows 10 IoT panels and for any third-party Windows 10 IoT device running the same HMI runtime. Below: what changed between EWF and UWF, what the filter state does to a download, the two deployment cases, the test that settles it, and the arithmetic for sizing the overlay while the filter runs.

EWF to UWF: what changed on Windows 10 IoT #

Windows 7 Embedded panels protected their system drive with EWF, the Enhanced Write Filter: sector-level protection where writes could be discarded or committed to the volume later. A Vijeo Designer project under Machine Expert v2.0 managed that filter during downloads, which is the workflow behind this question on Magelis HMIG5U2-class hardware.

Windows 10 IoT uses UWF instead. UWF blocks writes to the protected volume and redirects them into a virtual overlay; nothing reaches the disk unless it is committed. The filter is managed on the device with uwfmgr.exe, or remotely by MDM tools through the UnifiedWriteFilter CSP and the UWF WMI interface. Microsoft documents the move from EWF to UWF as a migration between different filters, not a setting that carries over. Decision: treat the old automatic download handling as gone until a test on your own hardware proves otherwise.

What the filter state does to a project download #

With the filter on, a transfer writes its files into the overlay. The progress dialog reports success because the runtime sees its own files. The next restart discards the overlay and the panel boots the previous project. With the filter off, the writes reach the disk and the project survives.

Does the download tool flip the filter first, as it managed EWF on the Windows 7 Embedded builds? No published behavior for the Windows 10 IoT targets says it does. Plan on the tool ignoring the filter and you are covered either way: if a future build does manage it, your explicit state change and restart check still end at the same verified result.

The two deployment cases #

Keep the targets separate, because they answer to different documentation.

Case 1 — the vendor's own Windows 10 IoT panel. For Magelis HMIG5U22 and HMIG5U2 hardware, Schneider Electric documents the UWF activate/deactivate procedure as FAQ000245569, a utility on the panel's Start Menu with an off/on switch. Use that procedure for every state change on this hardware; the old EWF toggle was a separate procedure and is not interchangeable.

Case 2 — a third-party Windows 10 IoT device running the same HMI runtime. The panel vendor's FAQ does not cover that hardware, and no documented behavior establishes automatic filter management during downloads on it either. Use the device supplier's documented UWF method, then prove persistence with the same restart test below.

Deployment target Documented filter procedure What you must prove
Magelis HMIG5U22 / HMIG5U2 on Windows 10 IoT Vendor procedure FAQ000245569 Download persists after a restart; final filter state matches production
Third-party Windows 10 IoT device with the HMI runtime Device supplier's documented method Same two checks, run on that hardware

The download-and-restart test #

Run the toggles and restarts in planned downtime; a panel that reboots mid-cycle leaves the machine without a working operator interface.

  1. Record the baseline: panel model, operating system build, runtime version, project software version (Vijeo Designer under Machine Expert v2.0 in the setup this article answers), and the current filter state.
  2. Back up the running project and its runtime configuration to storage outside the panel. If a filter mistake leaves the panel locked or empty, redownloading an HMI project after a user lockout covers the recovery path.
  3. Set UWF off with the procedure for your case, then restart so the new state takes effect.
  4. Download a controlled test revision: put an unmistakable marker on one screen, such as a version text reading UWF TEST 1, and keep everything else identical to production.
  5. Restart once and open the marker screen. Marker present means the download persisted with the filter off, so the storage path works.
  6. Set the required running state — filter on for production — and restart again.
  7. After the second restart, confirm the project starts on its own and the marker screen is still there. That proves the final filter state still boots your project.

Reading a failure: a missing marker at step 5 with the filter off points to a download or storage fault, not the filter. A missing marker at step 7 means the final state change or its restart lost the project — repeat with the filter left off and settle the state procedure before the panel returns to production.

Accept the workflow on this evidence #

Accept the panel for production only when all three hold after the final restart: the test revision is running, the runtime configuration you recorded in step 1 is present, and the filter state matches the production requirement. A clean transfer dialog or a good download log is not acceptance evidence, because a transfer also unsettles runtime data: values that lived in volatile memory reset around a project transfer, as why HMI variable values reset after a project transfer explains. One restart-and-confirm pass settles the files and the values together.

Overlay headroom while the filter runs #

With the filter on, the runtime keeps writing: alarm logs, trend buffers, recipe saves, system events. Those writes land in the overlay, which the restarts in your maintenance cycle empty, so size the overlay against the longest gap between restarts the production schedule allows.

Worked example, with example inputs rather than vendor defaults: set the overlay ceiling to 2048 MB in the filter's configuration and measure the panel's daily writes at 40 MB per day from a week of log and trend files. Headroom is 2048 MB ÷ 40 MB/day = 51.2, about 51 days. A noisier panel writing 150 MB per day gives 2048 MB ÷ 150 MB/day = 13.7, about 13 days. Decision: keep the restart cadence below the day count your measured rate produces, and raise the overlay ceiling when that cadence does not fit the schedule. The input that moves the number is your own measured write rate, so measure it on the panel instead of assuming it.

The decision, case by case #

  • Magelis HMIG5U22 or HMIG5U2 on Windows 10 IoT: manage UWF explicitly with the procedure documented in FAQ000245569 — filter on for production, off for downloads you must guarantee on disk, and every state change proven by the restart test above. Run the full test at first commissioning and after any project software upgrade, since download behavior is exactly what an upgrade can change. If the panel behaves otherwise, take the baseline from step 1 to the vendor's support channel.
  • Third-party Windows 10 IoT device with the HMI runtime: the same decision with the supplier's procedure. Nothing documented establishes automatic filter management on that hardware, so the restart test is not optional there.
  • Coming from Windows 7 Embedded panels: the EWF workflow does not carry over, so write the filter test into the replacement plan in planning an HMI terminal replacement from an older operator panel.

Questions asked

Does a Vijeo Designer project download manage UWF on Windows 10 IoT?

No published behavior states that it does, so treat it as unverified rather than assuming the Windows 7 Embedded EWF workflow carried over. Set the filter state yourself before and after the transfer, restart, and confirm the downloaded revision is still running. If a controlled test on your hardware proves the download toggles the filter reliably, you can shorten the routine, but keep the restart check in every commissioning.

How do I switch UWF off or on on the vendor's Windows 10 IoT panel?

Follow the vendor's documented procedure, FAQ000245569: open the write filter utility from the panel's Start Menu, move the off/on switch, confirm, and restart so the new state takes effect. Note the state before you begin and set the required state again after commissioning. On third-party Windows 10 IoT hardware that procedure does not exist; use the device supplier's documented method instead.

What manages UWF on a third-party Windows 10 IoT device?

Windows manages the filter through uwfmgr.exe on the device itself. Remotely, MDM tools handle it through the UnifiedWriteFilter CSP or the UWF WMI interface. State changes take effect after a restart, so build one into the procedure. The HMI software vendor's panel FAQ does not cover that hardware; the device supplier's documentation is the authority for how the filter is configured on it.

What should I send the panel vendor when download behavior looks wrong?

Send the complete baseline: HMI model, operating system build, runtime version, project software version, the filter state before the download and after the final restart, and the restart result from a controlled test revision. That set lets support reproduce what you saw instead of guessing from a failed transfer alone. Keep the test project small and nonproduction so the reproduction is quick.

Keep reading

  • Troubleshooting

    Fixing HMIRTM.EXE Runtime Crashes on a Comfort Panel

    The HMIRTM.EXE serious error is the HMI runtime crashing on the panel itself, most often because internal storage filled with accumulated logs. Back up to a USB stick from the panel operating system, delete the logs, and stop the runtime before changing the IP address; the failed ping is a network fault that sits below the project layer.

    HMI and touchscreens

  • Troubleshooting

    Getting the Right Firmware File for a Legacy HMI Panel

    Before you chase a firmware file, decide which of three things the panel actually lacks: a communications fix, an application restore, or an operating-system image. A panel that boots and navigates almost never needs firmware, and the only safe source for the image is the manufacturer or an authorized distributor, matched to the exact nameplate model and revision.

    HMI and touchscreens

  • How-to

    How One Spare HMI Panel Covers Seven Machines

    Yes. Keep one backup archive per machine on a USB stick or memory card, and restore the needed archive to the single spare panel at the panel itself. This works without WinCC flexible only if the backup transfer option was enabled when each project was downloaded; otherwise you need a PC with ProSave, and archives restore only to the same panel model.

    HMI and touchscreens