Svoboda | Graniru | BBC Russia | Golosameriki | Facebook
Jump to content

Talk:360 Safeguard

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
WikiProject iconComputer Security: Computing Low‑importance
WikiProject iconThis article is within the scope of WikiProject Computer Security, a collaborative effort to improve the coverage of computer security on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
LowThis article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing (assessed as Low-importance).
Things you can help WikiProject Computer Security with:
Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...
  • Answer question about Same-origin_policy
  • Review importance and quality of existing articles
  • Identify categories related to Computer Security
  • Tag related articles
  • Identify articles for creation (see also: Article requests)
  • Identify articles for improvement
  • Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
  • Find editors who have shown interest in this subject and ask them to take a look here.

lol…

[edit]

This program is as safe as inviting chinese commies to your home. Highly dangerous and suspipcious piece of bloatware. Stay away from it for your own sake. 51.68.152.226 (talk) 10:11, 18 November 2018 (UTC)JG[reply]

I tried to deinstall (even manually in safe mode) and it always sneaked in the 360Sandbox again. The respective registry keys were protected from access or deletion (even to Administrators and System). I'd say this is classical trojan behavior. I've yet to figure how to finally remove it fully. It's way harder than anything i've seen before! -- a Windows10 user — Preceding unsigned comment added by 93.214.248.208 (talk) 02:27, 26 March 2019 (UTC)[reply]