# FMP URL not working on Windows 10

**URL:** <https://the.fmsoup.org/t/fmp-url-not-working-on-windows-10/4430>\
**Category:** Floating Topics\
**Created:** [October 29, 2024, 3:58pm UTC](https://the.fmsoup.org/t/fmp-url-not-working-on-windows-10/4430 "2024-10-29T15:58:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rivet](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/rivet/32/1727_2.png) [@rivet](https://the.fmsoup.org/u/rivet)\
**Post date:** [October 29, 2024, 3:58pm UTC](https://the.fmsoup.org/t/fmp-url-not-working-on-windows-10/4430/1 "2024-10-29T15:58:24Z")

</div>

I have a solution that has been archived from a MAC to a Windows 10 Pro machine. There is an issues where `FMP://` URL WebViewer links trigger this prompt.

 ![fmp_URL_windows](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/a/a1bff34e51ede43fcfd615088b96d86765b22a6f.png)

.

I thought this might be the anwswer:

> **[Stop the FMP URL Prompts in FileMaker 19.3 for Windows - SeedCode](https://seedcode.com/stop-the-fmp-url-prompts-in-filemaker-19-3-for-windows/)**
>
> Thanks to Christian at Monkeybread Software, we now have a way to tell the web viewer that we don't need to be prompted every time we use an FMP URL.

//my settings

 ![Screenshot 2024-10-29 at 8.49.17 AM](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/0/047e497086e8713bf0a307508ae2bbeb4743e9aa.png)

but no luck

```auto
FMS: 21.x
FMP: 21.x
Window: 10 PRO

```

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [October 29, 2024, 8:59pm UTC](https://the.fmsoup.org/t/fmp-url-not-working-on-windows-10/4430/2 "2024-10-29T20:59:35Z")

</div>

@rivet Does the file name contain a space char? Recently I read some posts elsewhere indicating similar troubles. There was a mention that removing any space chars from the file name solves the issue.

My guess would be that there's been an unexpected change in how URL encoding is being handled by the underlying browser, whereby, what used to be a properly escaped space char, i.e., %20, is now being extra-escaped, resulting in the problem folks are seeing. This is totally just a guess, however, and should be taken with a grain of salt.

If it does seem plausible that this is due to an escaping issue, and it is not possible to rename the file to not have space chars, I wonder if using a + char to encode the space in the URL would fare better than %20.

And, if all this is off-base because the file in question for you does not even have a space char in its name, then apologies for the noise.

---

<div class="post-metadata">

**Author:** ![rivet](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/rivet/32/1727_2.png) [@rivet](https://the.fmsoup.org/u/rivet)\
**Post date:** [October 29, 2024, 11:51pm UTC](https://the.fmsoup.org/t/fmp-url-not-working-on-windows-10/4430/3 "2024-10-29T23:51:16Z")

</div>

Thanks @steve_ssh for the suggestions, they nudged me to the solution. The old URL's were `fmp://%24` so a global search and replace to `fmp21://$` did the trick. 🙏🏼