# Important bug for Windows Users when starting KNIME **URL:** \ **Category:** KNIME Analytics Platform\ **Tags:** bug\ **Created:** [September 17, 2024, 1:44pm UTC](https://forum.knime.com/t/important-bug-for-windows-users-when-starting-knime/83291 "2024-09-17T13:44:15Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![JPollet](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/j/958977/32.png) [@JPollet](https://forum.knime.com/u/JPollet)\ **Post date:** [September 17, 2024, 1:44pm UTC](https://forum.knime.com/t/important-bug-for-windows-users-when-starting-knime/83291/1 "2024-09-17T13:44:15Z")
Hi, I quote the title of an another post ([Important bug for Mac Users when starting KNIME](https://forum.knime.com/t/important-bug-for-mac-users-when-starting-knime/83274)) because the problem seems to be the same for Windows (Windows 10 and Knime 5.3.2) : when starting Knime, it open an empty workspace and I need to swicth workspace to the correct one. No Windows update, no Knime update since yesterday (when Knime works correctly). Best, Joel ---
**Author:** ![VAGR\_ISK](https://forum-cdn.knime.com/user_avatar/forum.knime.com/vagr_isk/32/64532_2.png) [@VAGR\_ISK](https://forum.knime.com/u/VAGR_ISK)\ **Post date:** [September 17, 2024, 2:08pm UTC](https://forum.knime.com/t/important-bug-for-windows-users-when-starting-knime/83291/2 "2024-09-17T14:08:34Z")
Hi, It seems to me that KNIME developers are trying to update the platform and modified the option to choose the different workplaces at the beginning when someone opens the program. I observed that if you have the workspace in a different place than the default, KNIME will create a workplace automatically with all the default workflows and with this the configuration for conda and python is also reset. That is why I think that will also affect windows users because is more a new feature than a failure. Just, it is bad for people having the workspace in a different place than the default place. I am unsure why they changed this but, I was pretty happy with the previous functionality. In any case, I did not observe any deletion of information. Cheers, AG. ---
**Author:** ![JPollet](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/j/958977/32.png) [@JPollet](https://forum.knime.com/u/JPollet)\ **Post date:** [September 17, 2024, 2:24pm UTC](https://forum.knime.com/t/important-bug-for-windows-users-when-starting-knime/83291/3 "2024-09-17T14:24:41Z")
Hi @VAGR_ISK, Thanks for this explanation. Indeed my workspace is not in the default place. And there is a reason for this : the default workspace is far from the root and produce long paths which produce error for some backup systems. It could be difficult to adapt to this new configuration. Best, Joel ---
**Author:** ![mlauber71](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mlauber71/32/73590_2.png) [@mlauber71](https://forum.knime.com/u/mlauber71)\ **Post date:** [September 18, 2024, 8:01am UTC](https://forum.knime.com/t/important-bug-for-windows-users-when-starting-knime/83291/4 "2024-09-18T08:01:59Z")
Maybe continue discussion here: > [@Important bug for Mac Users when starting KNIME](https://forum.knime.com/t/important-bug-for-mac-users-when-starting-knime/83274): > > Hello, I’ve encountered an issue with KNIME Analytics Platform after the latest update on my Mac. When I open KNIME, it automatically tries to open a specific workspace repository that I did not create or set as default. It creates this workspace on my computer without my consent and ignores my actual workspace, which is located in a different directory. Even when I delete this unwanted workspace, it reappears the next time I open KNIME, forcing me to manually change the workspace location eve… @VAGR_ISK @JPollet and there seems to be a solution: update your Palladian extensions to the latest version > [@Important bug for Mac Users when starting KNIME](https://forum.knime.com/t/important-bug-for-mac-users-when-starting-knime/83274/7): > > So, here’s my Road to Canossa: This one is on me - I am sorry! Turns out that the recent updates for the Palladian and Spellchecker nodes had a bug which caused this issue on KNIME 5.3. There’s updates for Palladian ([v3.1.2](https://nodepit.com/product/palladian/changelog#version-3-1-2-2024-09-18)) and Spellchecker ([v1.3.3](https://nodepit.com/product/spellchecker/changelog#version-1-3-3-2024-09-18)) available now which address this. Please install the updates, restart KNIME, select the proper workspace location once again and all should be back to normal. FAQ: Did the bug lead to any data loss? - No. Which KNIME versions were affected? …