Hi,
Unfortunely, clicking the link to download file triggers an error message:
ERROR: (Forbidden)
We were unable to satisfy your request due to access control:
Regards,
LeoEG1
Deze browser wordt niet meer ondersteund.
Upgrade naar Microsoft Edge om te profiteren van de nieuwste functies, beveiligingsupdates en technische ondersteuning.
Replying to a text message in Windows Phone Link works fine. But when starting a new message by clicking the "New message" button does not work. The waiting cursor is displayed and after a few seconds, the app exists. No new message is launched. Neither an error message.
Recent messages are displayed in the app and can be replied to. Searching for a contact in the app yields no results.
The problem occurs on my Windows 10 PC, but also in exactly the same way on a Windows 11 PC.
I have already completely uninstalled and reinstalled the app in Windows, but that does not solve anything.
I also removed and reset the link between the phone and the PC.
Windows is fully up to date, the Phone Link app has been reinstalled from the Microsoft Store, the phone's software is up to date and the Link to Windows on the phone is also up to date.
How can this issue be resolved?
Thanks.
LeoEG1
----
My system:
windows 10 Version 22-12 (OS Buid 19045.2728)
Windows Update: You’re up to date (22H2)
Phone: Samsung Galaxy Note20 Ultra 5G
Link to Windows App:
Version: 1.2301 2.43.0
Link to Windows Service Version: 2.6.03.1
The latest version is already installed.
Android Version 13.
Software update: the latest version is already installed.
Vergrendelde vraag. Deze vraag is gemigreerd vanuit de Microsoft Ondersteuning-community. U kunt met een stem aangeven of de inhoud nuttig is, maar u kunt geen opmerkingen of antwoorden toevoegen of de vraag volgen.
Hi,
Unfortunely, clicking the link to download file triggers an error message:
ERROR: (Forbidden)
We were unable to satisfy your request due to access control:
Regards,
LeoEG1
Hi,
The workaround is installing the new package I linked above, which is for Beta Channel and does not have the issue.
I am pretty hopeful that the same will resolve the issue.
Hi,
Thank you for the link.
Where can I find more information about the workaround?
Regards,
LeoEG1