Windows 10 updates - how to make them go away for good.
-
Great! I was looking for a particular "Administrative Priviledge" elevation method without having to reinstall an olde software under elevated (to run-as-administrator) CMD ... and seeing the GP Editor interface restored my recollection of having done it before using the very same. Unfortuneately, this is not going to be easy ... to FIND the cruddy install that is flagging my attempt at running it by right-click elevating and running as administrator (due to drivers THAT WILL NEVER BE SIGNED FOR WINOWS 10; duh!) ... because GPEdit.exe has no immediate facility to look through it's "policies" and get the location where all the unaltered STATES (Not Configured) for the olde app reside. There's a filter mechanism but no dedicated interface to the policies. Perhaps you might know the exact location under which installed software hoists it's petard so an OWNER can do some mechanical SETTING changes? Administrative Templates, surely ... but where exactly? (apologies to all ahead of time for hijacking a thread to make my own personal gains expedient)
Well, if you want to see the "Resultant Set Of Policies", you need to run rsop.msc, it will tell you which policies are set to something else than default.
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
Well, if you want to see the "Resultant Set Of Policies", you need to run rsop.msc, it will tell you which policies are set to something else than default.
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
Also, if you want to change privileges you should take a look at secpol.msc, that's where those things reside.
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
Also, if you want to change privileges you should take a look at secpol.msc, that's where those things reside.
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
Wow. Thanks for that as well. Here's what I found using just GPEDIT.MSC ... (long story shortened) ... there's no way to do what I want to do because it's already done! Which is what I feared, and what rsop.msc so adeptly makes clear ("snap-in" filter probably), DISABLED is the "User Account Control: Use Admin Approval Mode for the built-in Administrator account". And because there's no signed driver there's really only default-at-install behavior going on so the app runs at dismal complete "blocked for your protection" anyway. That's it. I'll just uninstall it, restart, and run the setup again under elevated command prompt from a DOS window. (wrt secpol.msc -> it still is weird to me how, under Security Options the Policy "User Account Control:Run all administrators in Admin Approval Mode" could be ENABLED but one is getting the big red UAC block anyway)
-
Wow. Thanks for that as well. Here's what I found using just GPEDIT.MSC ... (long story shortened) ... there's no way to do what I want to do because it's already done! Which is what I feared, and what rsop.msc so adeptly makes clear ("snap-in" filter probably), DISABLED is the "User Account Control: Use Admin Approval Mode for the built-in Administrator account". And because there's no signed driver there's really only default-at-install behavior going on so the app runs at dismal complete "blocked for your protection" anyway. That's it. I'll just uninstall it, restart, and run the setup again under elevated command prompt from a DOS window. (wrt secpol.msc -> it still is weird to me how, under Security Options the Policy "User Account Control:Run all administrators in Admin Approval Mode" could be ENABLED but one is getting the big red UAC block anyway)
Ok, then you need to restart into troubleshooting mode. Go to the start menu and click "Restart" while pressing down the shift button. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button. When the computer restarts you will get some choices, one of them will be “Disable driver signature enforcement.”
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
If I buy the computer how I am thinking to buy it a Windows VM running under Linux will still have more resources available as my current main computer. I will buy it with Windows 10 professional, then format and clean reinstall, do an image... and then give it a try. If it annoys me as I am already experiencing with support at my relatives... I think I try Linux pretty soon, and then decide what I do with my main OS. But for all what you say... I think a VM will do it.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
One of the solutions I tried, years ago, was running Windows in a VM. Virtualization technology was less mature than it is today, the hardware support not like on modern CPUs. So some drivers wouldn't run. And performance was sluggish - maybe not for lengthy, CPU-intensive processing; it was more a problem of latency: immediate response like keyboard echo on screen and mouse handling felt as if signaling through a rubber band. A few years ago, we introduced VMware at work (as a test configuration management tool, to be able to run exactly the same test setup ten years later, without regard to underlying hardware) - I guess most people consider VMware as "mature" technology. All drivers relevant for our setup did work, but we experienced significant latency in the USB handling - so bad that the test driver had to be modified to handle it. When going from USB2 to USB3 (we needed the higher capacity; the software/firmware to be downloaded to the device under test had increased by orders of magnitude in a few years), we dropped the virtualization and searched for other ways of test configuration management. I may be setting up a VM machine at home. Every now and then, I pick up some old Win16 software that won't run on a 64-bit Windows 10, but I can run it on my old Windows 98 license. Another VM can run some *nix, for the few things where *nix software can do things significantly better. But for my everyday tools, I will avoid driver issues and latency/performance issues by running directly on physical, non-virtual hardware. I sure recognize that VMs today are different from what I tried to make work 10+ years ago, but the more recent experiences at work tells me that I am far safer if the hardware is real, not only something pretending to be hardware, especially when doing low level programming. If the majority my everyday tools were *nix based, I guess I would opt for running on a *nix base, with Windows in a VM. That is not the case. I leave VMs for the less used tools. For me, that includes Win98 and *nix.
-
Ok, then you need to restart into troubleshooting mode. Go to the start menu and click "Restart" while pressing down the shift button. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button. When the computer restarts you will get some choices, one of them will be “Disable driver signature enforcement.”
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
It's Saturday man! You must be crazy ... etc ... ( I must admit, too, that having just two days ago experienced a Windows 10 blue-screen event where my Video Memory Block got flipped, that doing anything on the computer to show me that Advanced Options screen again so soon, especially on the weekend, is not going to be in my plans ... for a WHILE ;P ) And for you kids out there following along in this thread: be sure, when you go to start/restart Windows 10 after a BSoD event, to be in VGA ONBOARD MODE and have that analog connection to your extended desktop monitor hooked up with power to the display ... because when Win 10 goes into "troubleshoot" mode, you better not be relying on your HD graphics card video and HD monitor to do anything but enable a dance in the darkness ... under a flickering HDD-LED-lit light! Go ahead, young'n ... hit the reset button on the exterior of your box dispite being warned not to turn yours off during the act of recovery. Make Windows 10's day.
-
It's Saturday man! You must be crazy ... etc ... ( I must admit, too, that having just two days ago experienced a Windows 10 blue-screen event where my Video Memory Block got flipped, that doing anything on the computer to show me that Advanced Options screen again so soon, especially on the weekend, is not going to be in my plans ... for a WHILE ;P ) And for you kids out there following along in this thread: be sure, when you go to start/restart Windows 10 after a BSoD event, to be in VGA ONBOARD MODE and have that analog connection to your extended desktop monitor hooked up with power to the display ... because when Win 10 goes into "troubleshoot" mode, you better not be relying on your HD graphics card video and HD monitor to do anything but enable a dance in the darkness ... under a flickering HDD-LED-lit light! Go ahead, young'n ... hit the reset button on the exterior of your box dispite being warned not to turn yours off during the act of recovery. Make Windows 10's day.
Well, the Wife and kids are watching a movie I can't stand, so I'm sitting here with some bourbon watching ACDC videos... :) That's where you can always trust laptops, monitor won't fail in troubleshooting mode. Well unless the monitor is the problem. ;P
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
Well, the Wife and kids are watching a movie I can't stand, so I'm sitting here with some bourbon watching ACDC videos... :) That's where you can always trust laptops, monitor won't fail in troubleshooting mode. Well unless the monitor is the problem. ;P
Wrong is evil and must be defeated. - Jeff Ello Never stop dreaming - Freddie Kruger
-
One of the solutions I tried, years ago, was running Windows in a VM. Virtualization technology was less mature than it is today, the hardware support not like on modern CPUs. So some drivers wouldn't run. And performance was sluggish - maybe not for lengthy, CPU-intensive processing; it was more a problem of latency: immediate response like keyboard echo on screen and mouse handling felt as if signaling through a rubber band. A few years ago, we introduced VMware at work (as a test configuration management tool, to be able to run exactly the same test setup ten years later, without regard to underlying hardware) - I guess most people consider VMware as "mature" technology. All drivers relevant for our setup did work, but we experienced significant latency in the USB handling - so bad that the test driver had to be modified to handle it. When going from USB2 to USB3 (we needed the higher capacity; the software/firmware to be downloaded to the device under test had increased by orders of magnitude in a few years), we dropped the virtualization and searched for other ways of test configuration management. I may be setting up a VM machine at home. Every now and then, I pick up some old Win16 software that won't run on a 64-bit Windows 10, but I can run it on my old Windows 98 license. Another VM can run some *nix, for the few things where *nix software can do things significantly better. But for my everyday tools, I will avoid driver issues and latency/performance issues by running directly on physical, non-virtual hardware. I sure recognize that VMs today are different from what I tried to make work 10+ years ago, but the more recent experiences at work tells me that I am far safer if the hardware is real, not only something pretending to be hardware, especially when doing low level programming. If the majority my everyday tools were *nix based, I guess I would opt for running on a *nix base, with Windows in a VM. That is not the case. I leave VMs for the less used tools. For me, that includes Win98 and *nix.