Thanks for your reply Steven. 

I have been following the same process as I have in Studio 2019. I receive the file from my customer, save it onto my hard drive and use the 'Add file' button in Studio 2021 to add the file. 

Once I press OK, the Trados screen is displayed without the file being added. Just to clarify, I am using the same folder that I used previously with Studio 2019 with the same permissions. 

In the interim, I am using Studio 2019, where I have been able to upload the same file from the same location. 

Very perplexing. By the way, on this error, I was not able to follow the steps you suggest as there was no save button.

Any suggestions are very welcome.

Gillian

Thanks for your reply Steven. 

I have been following the same process as I have in Studio 2019. I receive the file from my customer, save it onto my hard drive and use the 'Add file' button in Studio 2021 to add the file. 

Once I press OK, the Trados screen is displayed without the file being added. Just to clarify, I am using the same folder that I used previously with Studio 2019 with the same permissions. 

In the interim, I am using Studio 2019, where I have been able to upload the same file from the same location. 

Very perplexing. By the way, on this error, I was not able to follow the steps you suggest as there was no save button.

Any suggestions are very welcome.

Gillian

Hello Gillian Shaw

Apologies for the late reply (please see below on how to ensure whom you are responding to is notified- for a quick response).

You mention-

Gillian Shaw said:

I receive the file from my customer, save it onto my hard drive and use the 'Add file' button in Studio 2021 to add the file. 

-however the file appears to be saved to OneDrive as your screenshot shows, whereas the project is indeed local.

This appears to be very similar to the issue discussed here - (Office365/OneDrive)

https://community.sdl.com/product-groups/translationproductivity/f/studio/31815/problem-with-trados-studio-autosave-and-onedrive

Please try temporarily disabling OneDrive and then add the file to the project from the actual local folder where you saved it.

Hi

Many thanks - I shall try that. However I have to ask why this way of working has and currently still works for Studio 2019 but it does not work in Studio2021? 

Surely many users will be using the OneDrive storage as they had been doing before - like me. 

I shall come back to you when I have given your suggestion a try - probably tomorrow as I am busy for the rest of today.

Gillian

Hello Steven

Sorry for not replying sooner.

The problem very much remains. 

Let me share a few things:

1) I see no evidence the problem is with Microsoft OneDrive. Why? Because the problem is perfectly reproducible when Microsoft OneDrive is 'closed' (by selecting OneDrive in the Windows System Tray, right click, and selecting 'Close OneDrive'). The file I'm trying to add is perfectly readable and actually stored on the local device. For example, I can open the Microsoft Word document using Microsoft Word and it opens as you would expect. I'm not changing computer or Windows logon to do this. Its the same session and user and security as the user I'm using for SDL.

2) I see no evidence there's a problem with the file. Why? Because the problem is reproducible with all Microsoft Word documents where ever they are stored on the Windows C: drive. The same Microsoft Word documents open in SDL 2019 on the same device using the same logon and apparently everything meaning the only difference is the version of SDL (it appears)

3) I do see evidence that SDL is not Windows 10 complaint (for both SDL 2019 and 2021). Why? Because to properly install it and run it I have had to do the following:

3a) when installing: I had to change the Windows Settings - Windows Security- Virus & Threat Protection - Virus & Threat Protection Settings - Manage Settings - Real-time Protection - turn OFF. I then re-enabled this setting after SDL installed. The problem is reproducible with this setting OFF as much as it being ON.

3b) when installing and now also set: I had to change the Windows Settings - Windows Security- Virus & Threat Protection - Manage Settings - Exclusions (for Microsoft Defender Antivirus) - Add or remove exclusions - Add an exclusion 'C:\Program Files (x86)\SDL' folder and 'C:\Users\Gill\Documents\SDL'

(An application that is Microsoft Windows 10 compliant, wouldn't need these settings and indeed changes to this settings put me and my customers at risk, which is a concern to me).

4) I have performed a full 'repair' of SDL 2021 by selecting Windows Control Panel - Programs and Features - 'SDL MultiTerm 2021 Core' and selecting the 'Repair' option. The operation completed successfully without any warnings (I did set 3a above to all the non-Windows 10 complaint SDL product to complete without Windows 10 thinking it was a virus and trying to do something the non-Windows way)

5) My Windows 10 and Office 365 are full up-to-date as is my BIOS and other hardware drivers. I've completed a full reboot multiple times (a proper reboot, not just power or sleep!). My browsers are also up-to-date and I have an incredibile reliable internet connection! ;-)

6) I have applied SP2 of SDL meaning the Help-About shows '16.0.2.3343'. I do see that SP3 is now available. I will try that, but I can't see why that would be any different. Nevertheless I shall try that very soon (and using step 3a above)

7) My SDL account is signed-in and I have a valid license, though I have yet to enjoy the benefits of this license upgrade for I can not use this version of SDL at all. As a workaround I am using SDL 2019.

8) When reproducing the problem I do NOT see any violation in Windows Settings - Windows Security- Virus & Threat Protection - Current Threats - Protection History. This suggests the problem isn't because SDL isn't complaint with my Windows Security setting. (I believe SDL is not Windows complaint, but I've worked around that with the other settings). 

9) the workflow to reproduce the problem doesn't appear to matter. If I drag and drop (as source file), or right click in the project 'Add Files - Quick Add Files' , or 'Quick Add Files' from the toolbar. They all give the same error. 

10) attempting to create a new local project results in a dialogue titled 'Error' and SDL 2021 then becomes unresponsive. The dialogue box with 'Error' is empty of content:

After a while, SDL 2021 doesn't show as accessing any files (via Windows Resource Monitor), but it still consumes the whole of 1 CPU. I suggest this is evidence of a defect.

I'd be more than happy to try any other suggestions you have

Thank you again, Gillian

Happy New Year

I wonder if anyone has been able to look at this issue yet? I am still unable to use my 2021 software with confidence.

Many thanks

Gillian

Could you please try again deactivating temporarily your antivirus?

Hello Jesús Prieto, many thanks for your suggestion.

I have updated SDL 2021 to SP3 now and as I suspected, the problem is identical as with SP2.

I have though observed that when I disable "Windows Settings - Windows Security- Virus & Threat Protection - Virus & Threat Protection Settings - Manage Settings - Real-time Protection" , i.e I turn this OFF then this works around the problem. I found that it only works around the problem with the setting is OFF upon starting the SDL application. So, for example, if you leave this setting ON whilst starting the SDL application, but then turn it OFF, before attempting to reproduce the problem, you'll still reproduce the problem.

So, earlier when I said "The problem is reproducible with this setting OFF as much as it being ON.", this wasn't quite correct. Its only correct when the setting is OFF upon starting the application.

I therefore believe I've answered your question?

However, this workaround isn't a workaround that's acceptable. Its fundamentally critical that Antivirus is enabled the whole time to protect me and my customers that I work for, its part of my responsibility. It would be irresponsible for me to carry out work on a computer with Antivirus disabled and I could even be in breach of code of conduct for the bodies that I work for. 

I chose Microsoft Windows 10 as the Operating System because of its security features and I don't want to loose those features just because SDL isn't providing a Windows 10 compliant application. Indeed Microsoft make it clear that vendors, such as SDL, have a responsibility:

From docs.microsoft.com/.../certification-requirements-for-windows-desktop-apps:

The Windows platform supports a broad ecosystem of products and partners. Displaying the Windows logo on your product represents a relationship and a shared commitment to quality between Microsoft and your company. Customers trust the Windows brand on your product because it ensures that it meets compatibility standards and performs well on the Windows platform. Successfully passing Windows App Certification allows for your app to be showcased in the Windows Compatibility Center and you may display the certification logo on your site.

The same web page lists all the requirements for "[Windows 10] Certification requirements for Windows Desktop Apps"

I think we can probably agree that SDL falls short on one or multiple of these requirements?

If we agree to this, then we can say that SDL isn't fit for the purpose I need to use it for. This then leads to

1) Will SDL fix this? If so when?

2) If not, please issue a refund (I can still use SDL 2019 which I believe still isn't Windows 10 compliant, but at least I can keep the Real-time Protection enabled)

Many thanks

Gill

We are getting close!

I'd say that if you add an exception to your antivirus software, the Trados Studio problem will be solved and your antivirus will be running, as you wish.

Usually adding an exception means adding Trados Studio and Multi-Term EXE's to the antivirus exception list. Try it first, and if it doesn't work, come back and state the antivirus name, so someone can help you with the exact settings.

I've already listed SDL as an exception as I've documented above.

I'm using the default and standard Windows 10 endpoint security and all the settings are documented above.

As the vendor, if you can specify the exact steps needed to use your software with the default Windows 10 security settings, then please feel free to share them. I'm not aware that I'm able to make additional exceptions to what I've already done, but then I'm not the software vendor and I don't know how your product works, nor which Windows 10 compliant features its not fully respecting. Feel free to share the list of items SDL isn't complaint with for Windows 10 certification and I might be able to make a better judgement. A Windows 10 complaint application should NOT require any special configuration, especially any anti-virus setting, this tells me the software is behaving like a virus and doing things it really shouldn't be doing.

Just so we're clear, I'm still expecting :

1) Will SDL fix this? If so when?

2) If not, please issue a refund (I can still use SDL 2019 which I believe still isn't Windows 10 compliant, but at least I can keep the Real-time Protection enabled)

Many thanks again

Gill

I have nothing to do with SDL, I'm an end user just like you, willing to help.

There may be some reasons that can explain what's going on here, but I'd bet that the antivirus is the culprit, and you still need to do it for Trados Studio 2021. If I'm right, the fix is on the Windows side, your side.

Hello Jesús Prieto,

Many thanks for your contribution, as a volunteer this is much appreciated.

I need a response from SDL then, as I've presented plenty of evidence the problem is with SDL. I'm quite convinced the problem is with SDL 2021 client software and whilst I found a workaround, this isn't acceptable to me for the reasons explained earlier.

Perhaps I can ask for an official SDL response please?

I'm looking for SDL to reply to these questions:

1) Will SDL fix this? If so when?

2) If not, please issue a refund (I can still use SDL 2019 which I believe still isn't Windows 10 compliant, but at least I can keep the Real-time Protection enabled)

Many thanks again for Jesus and I hope SDL will be able to shed some light on this issue.

Gill