This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 22%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYH%3C/text%3E%3C/svg%3E)
Hello Everyone :)
Am having an issue with Workspace on Edge running on Version 116.0.1938.62 (Official build) (64-bit).
workspaces show the error when accessing them:"Error enable to load"
honestly couldn't understand what I need to do.Any help is highly appreciated because the tabs I moved to workspaces are quite important for me to access.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @Yang Hai ,
To get more information, I have some questions to confirm with you:
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 55.00000000000001%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
I have had the similar problem to you, and my solution is to go to the folder /onedrive/apps/Microsoft Edge/Edge Workspaces/, and delete them for these configs of workspaces are always stored in your own onedrive. Also, deleting all of them is to make sure you would've remove the error.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 6%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
This worked for me - thanks Perdred!
Hi @Yang Hai ,
Here's a possible solution for you: signing out of Microsoft Edge and then signing in again. Let's see whether this works for you.
If this solution does not work for you, please visit edge://workspaces-internals/, and then "Export to JSON". And you'll need to submit the information in the browser to Edge Dev Team via feedback (Alt+Shift+I) with the JSON file attached. Thank you for your understanding!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best Regards,
Shijie Li
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 26%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDH%3C/text%3E%3C/svg%3E)
I reported this error a couple of weeks ago with the feedback button in edge. I received an email that a team was working on the issue. Yesterday I got another email stating that the problem will be fixed in one of the next edge versions. Quote:
Good news!! On Feb 26, 2024, you shared with us this feedback: Arbeitsbereiche können teilweise plötzlich nicht mehr geladen werden. Die Arbeitsbereiche müssen[…]> We want to let you know that we fixed an issue that's related to this feedback in an upcoming update to Microsoft Edge.