From: nospam@needed.invalid   
      
   On Mon, 2/16/2026 9:00 PM, Daniel70 wrote:   
   > On 17/02/2026 3:06 am, J. P. Gilliver wrote:   
   >> On 2026/2/16 10:15:46, John C. wrote:   
   >>> Daniel70 wrote:   
   >>>> Mr Xi Ji Ping wrote:   
   >>>>> ohn C. wrote:   
   >>>>>> Take back   
   >>>>>> tech corporations from India & industry back from China.   
   >>>>>   
   >>>>> Ajay Banga gave a major interview about what should happen in 2026:   
   >>>>>   
   >>>>> https://youtu.be/IqBXFwg3fk4   
   >>>>>   
   >>>>> He talks about India, migration, and the youth jobs time bomb. I   
   >>>>> strongly recommend watching it to learn how to be successful in this   
   >>>>> dynamic world.   
   >>>>>   
   >>>>> Good luck, and I hope this will kick-start your self-education journey.   
   >>>>>   
   >>>> Hey, Mr Xi Ji Ping (WOW!! Does the general secretary of the Chinese   
   >>>> Communist Party and chairman of the Central Military Commission really   
   >>>> frequent this newsgroup??)   
   >>>>   
   >>>> I don't see what YOU quote and attribute to John C anywhere in John C.'s   
   >>>> original post .... so are YOU mis-attributing stuff??   
   >>>   
   >>> Daniel, he's quoting my signature file. You may have your news reader   
   >>> set to hide signature files.   
   >>>   
   >> And has completely snipped and then ignored what the main body of the   
   >> post is about.   
   >>   
   >> (For anyone still wondering about the subject: the answer seems to be   
   >> that nobody knows, but don't rely on it not happening - and there is a   
   >> registry patch that will stop Windows updating drivers, though it's not   
   >> clear whether that will stop it _removing_ them.)   
   >>   
   > Sorry!! WHAT?? MicroSoft allows you to install a registry patch that stops   
   the installation of registry patches that MicroSoft thinks you need!!   
   >   
   > WHAT??   
      
   We might call those registry edits.   
      
   But you're not really a technician.   
      
   The Registry is a file system. It can hold arbitrary objects such   
   as a binary blob. It can hold things as small as a Boolean. It   
   has permissions (Registry keys can be owned by TrustedInstalller,   
   and those are very hard for a user to modify).   
      
   The OS has GPEdit.msc which holds Policies for the OS. In corporations,   
   Policies can be "pushed out" to thousands of machines at a time. The   
   anchor for these, is a section of the Registry given over to registry   
   entries corresponding to the wishes of a policy.   
      
   Other areas of the Registry, are not parts of Policy. Yet, they still   
   control things. The Registry is a place to hold Application Preferences   
   for example.   
      
   A Registry Entry only has power, if an executable will "sniff it" and honor   
   the setting. If the executable code is removed or changed, a Registry   
   Entry may be a "powerless orphan". For example, release controls, over whether   
   your OS can update itself, there were a fair number of keys abandoned and if   
   you   
   looked at them you might say "if I flip this switch, something good will   
   happen".   
   Well, nothing sniffs those any more, so the settings do nothing. It's up to   
   you to decide, which ones might do something.   
      
   Sometimes, Registry settings are "known" but have not been physically   
   entered into the Registry. This means an executable sniffs for them,   
   and finds the entry does not exist. If a user "adds" the entry and   
   programs it correctly, suddenly a new degree of control is realized.   
   Somebody has to discover these (via blog entry, knowing someone at the   
   company, or by examination or observation of executable activities with   
   ProcMon). That raises the two cases then, Registry key exists but is not   
   instantiated, or Registry key is instantiated but nothing "sniffs" it.   
      
   *******   
      
   If someone identifies a set of Registry keys, and they appear to be for   
   the intended purpose, there are reasonably good odds they will work.   
      
   Eventually, the situation in question, "a printer will not install   
   with a V3 or V4 universal framework driver", that will come to pass.   
   It could be changed at W11 26H2, or Release of Rental W12. The two Reg settings   
   will likely work for the intervening period up to then. For a W10 user,   
   the setting should be effective. W10 is officially out of support and   
   changing the security footing (design change) to the OS should be   
   forbidden to the staff at this point. The year of free updates, those   
   are to plug CVE, not particularly to be making a cellphone out of W10.   
   But they'll make a cellphone out of any other thing under active design.   
      
   All OSes eventually stop. Some are financed past their best before date.   
   In addition, technology companies are not particularly gifted at   
   business continuity, they make mistakes, they stumble and they are gone.   
   Having a big pile of cash will not save you, because you're not   
   humble, you squander the cash, and eventually you hit a wall and are gone.   
   IBM, for example, is still around. But really, for how long ? Some companies   
   that had depth, are now sheets of thin paper, waiting to be blown away.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)