# Internet Shortcut Problem

**URL:** <https://resource.dopus.com/t/internet-shortcut-problem/27171>\
**Category:** Help & Support\
**Created:** [October 23, 2017, 10:22am UTC](https://resource.dopus.com/t/internet-shortcut-problem/27171 "2017-10-23T10:22:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jaspi](https://resource.dopus.com/letter_avatar_proxy/v4/letter/j/ea5d25/32.png) [@Jaspi](https://resource.dopus.com/u/Jaspi)\
**Post date:** [October 23, 2017, 10:22am UTC](https://resource.dopus.com/t/internet-shortcut-problem/27171/1 "2017-10-23T10:22:50Z")

</div>

If i make an internet shortcut created by dragging from the Chrome address bar to the DOpus Lister and try to use i have the fallowing Error Code:  
"The target "" of this Internet Shortcut is not valid. Go to the Internet Shortcut property sheet and make sure the target is correct."  
when i click ok to the warning dialog appear another with the fallowing message:  
"Unable to open Internet Shortcut "......" "  
I realized that depending of the path where i create the shortcut will work or not:  
if my folder contains language specific (ex hungarian) letters will not work  
(ő, ű, Ő, Ű)

What i can do?

---

<div class="post-metadata">

**Author:** ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)\
**Post date:** [November 1, 2017, 4:18pm UTC](https://resource.dopus.com/t/internet-shortcut-problem/27171/2 "2017-11-01T16:18:23Z")

</div>

We should have a fix for this in the next update.

---

<div class="post-metadata">

**Author:** ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)\
**Post date:** [November 1, 2017, 6:07pm UTC](https://resource.dopus.com/t/internet-shortcut-problem/27171/3 "2017-11-01T18:07:13Z")

</div>

This turns out to be a bug in Windows (ieframe.dll, which gets involved in .URL launches even when Chrome is the default browser). You can see that the proper path has been sent to the command line, but it then tries to access what looks like a Unicode-\>ANSI/OEM conversion of the path.

 ![Clipboard Image](https://resource.dopus.com/uploads/default/original/3X/7/b/7bdec0a816b2fffb784f2f44e2daceaa61af2c54.png)

We have a workaround which fixes the problem, and that will be part of the next update.