Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
We're waiting on your proof that you didn't lie.
Until then - don't expect anyone to take you seriously.
For the record - the Registry isn't as powerful as it used to be in terms of influencing changes - that said - its not fragile either.
Microsoft keeps sneaking in little "minions" or "daemons" that undo/change/fiddle with keys as you go about your day.
So it takes a great deal of patience and know how to deal with it.
Every document on the net tells you to back up your registry hive before you change it. To be careful not to go around with a machete.
Even Mega whom we all caught with his pants down uses it too.
Like it or not - its a useful tool.
But like any tool - even installing 3rd party software (which is a far greater risk mind you) is just as dangerous.
So is crossing the street.
You have no idea what the GPE is - and I seriously doubt you even know how to get there let alone have access to it.
So please stop misinforming people and back up your claims with documentation from Microsoft.
I never said I could stop you.
But that won't stop me from calling your lies out either.
editing by hand is less dangerous than relying on 3d party tool. and it's better for self education :)
tho I have no idea what you can do wrong to registry as it will only affect the record you're editing. it won't break whole system.
Thus far there is nothing in GPE to make something totally unusable on a reboot, without easily fixing it in GPE after making the change.
Even if you were silly and say like, disabled Windows Installer, preventing people from installing software, the account you logged into to make the change, can easily undo it.
And even if you manipulated User Rights Management in GPE, you can't lock yourself out, just other users.
Like I said, there's nothing you can do, that you cannot undo under the same account.
You had to google that didn't you?
You really have no clue at all how GPE works.
As I said - back it up with Microsoft Documentation - or stand forever called a "newb"
And don't get cute with me kiddo - your argument for "Destroy your windows machine" argument for using GPE.
Or you are a liar - and everyone pretty made that conclusion.
Key point - only available to those who have Windows 10 Pro (11 Pro as well)
Otherwise its a feature locked out for normal use.
So not everyone has access to this powerful tool and eventually ends up mucking around in the registry - which frankly is more dangerous (but not that dangerous) compared to GPE.
GPE is rather harmless in comparison.
GROUP POLICY EDITOR - NOT SERVICE MANAGER / STARTUP MANAGER
You can't tell it to shut down or not launch explorer - you would need a script for that.
If your going to argue your case - at least bother to know what the heck your talking about!
GPE is designed to enforce policies in an Active Directory environment.
Restricting Software yes - but key Operating System components - no.
Enforce Operating System behavior - such as not updating beyond parameters - going to sleep at specific times - locking screen for security reasons - yes.
But, say you did disable the run command fully, you do know the shortcut to the .msc file is on the hard drive, and easily found in System32, yes?
And it's a policy editor, not a service manager. So how are you disabling windows explorer in it?
as if you ever took any responsibility for your lies and misinformation. you should be the last person to preach about responsibility.
He likely has never ever touched it until today.
Prob never touched Powershell either.
He's likely leeching off of us for education purposes only to become more irate.
See? This is what I'm talking about.
He won't read a word - just rambles off as if he knows everything.
You saw it here first folks - total fake.
"And it's a policy editor, not a service manager. So how are you disabling windows explorer in it?" <<<<< Proof right here - you don't know what you are talking about as Kom pointed out.
I expect you to answer him.