i have got a huge problem. Basically i cant work with UiPath anymore because UiPath crashes when i try to edit an argument. Same thing happens when i click on the namespaces. Any idea how to solve this problem? Im working with UiPath at a client. I did not change anything. Maybe the problem occurs because the IT changed to .netFramework Version or something? Thanks for any ideas!
Updating UiPath is not that easy, since we are automating tasks in a core banking system. The current version is approved by the core banking system supplier while newer version are not yet approved.
This happen in the old 2017 version. if you have large work flow it will crash… while editing arguments…
work around: if you split your WF into small parts and invoke them as needed then it won’t crash again.
give a try… if possible…
Large Workflows are not the problem. UiPath crashes even if i create a new workflow and try to add a new argument. Im sure it has something to do with the .NET Framework Update.
The clients IT wont downgrade .NET Framework. Is there any chance to get UiPath working again with another Windows-Update?
@MartinK if you verify in your latest windows update security fix and take a screenshot and post here.
That would be helpful further to fix or work around… to resolve your issue.
About the .NET Framework 4.7.1
The .NET Framework 4.7.1 is a highly compatible and in-place update to the .NET Framework 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, and 4.7. However, it can run side by side with the .NET Framework 3.5 Service Pack 1 (SP1) and earlier versions of the .NET Framework.
When you install this package, you can see that it’s installed as Update for Microsoft Windows (KB4033369) under the Installed Updates item in Control Panel.
The .NET Framework 4.7.1 is available on Windows Update and on Windows Server Update Service (WSUS). It will be offered as a recommended update on Windows Update.
Note A recommended update may be installed automatically on all supported platforms based on your computer settings on Windows Update.
I advise just remove this KB4033369 and restart your machine… this is recommended update but not mandatory. Hope this will fix your issue…