• Registry Adjustments for ALL, W 7, W 8.1 and W 10

    Home » Forums » Tools » Registry Adjustments for ALL, W 7, W 8.1 and W 10

    Author
    Topic
    #96121

    Registry Adjustments for ALL, W 7, W 8.1 and W 10

    I have watched the System messing with my registry setting in W 10 Fast Ring right before my eyes in RegEdit….

    Solution: Take possession of the Registry Key(lowest Mother) Restrict “System” to Read only and then I had to ‘Deny’ System Access to everything else!!! They haven’t changed since, EVEN THROUGH Upgrades. However, if they ever do that from “Trusted Installer”, Lord Help US ALL!

    Now!!! Backup, Backup, Backup your Registry, your Image. I don’t TRUST Restore Points to protect me BUT that is up to you. You can screw your Image up really Bad it you make mistakes here!!!!

    https://www.askwoody.com/forums/topic/paragon-ssd-and-hdd-backup-and-management-tools-free-and-paid/

    Registry Backup OR Restore Points(if they work for you, AND you trust them!) Do one or the other MAYBE Both!:

    https://www.askwoody.com/forums/topic/tweaking-com-registry-backup/

    MSDN Channel 9: “The Defrag Show” and “Defrag Tools” for Windows, Sysinternals, Core and Kernel Exploration

    https://www.askwoody.com/forums/topic/msdn-channel-9-the-defrag-show-and-defrag-tools-for-windows-sysinternals/

    This is where my Registry Adjustments started, to Manage and Control WU on MY System as far back as W 7.

    KB939844 Configure Automatic Updates using Registry Editor
    https://technet.microsoft.com/en-us/library/dd939844(v=ws.10).aspx

    Even though this was last updated in 2011 it was current when I started using it on W 7, and I have no reason to believe that, that is still not the case. The bottom section is for the “Client” side. If one sets the other keys as I do, “AUOption” would automatically be set to ‘1’ by the system up to W 8.1. If you look at “AUOption” the Range is 2-4. ‘1’ is AU off as I said set by the system. In W 10.0 1607 they have started letting it float, so I am setting it to ‘1’ for the system.

    The new one in W 8.1 is about OS Upgrade in it various “Names/values”. It is also in W 10.0, like that too.

    Here is my Registry Scripts ext= .reg without the Permission adjustments (those are done manually and so far only needed on W 10 Fast as well as when it RTMs):

    REG WU AU Windows Update Turned Off in Windows.reg (W 7)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    “NoAutoUpdate”=dword:00000001
    “NoAutoRebootWithLoggedOnUsers”=dword:00000001

    REG WU AU Windows Update, OSUPGrade, REBoot Turned Off.reg (W8.1 & W 10.0.14393.0 or Later, at a minimum)
    Interestingly enough W 10.0 1607 has lined back up with W 8.1.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    “DisableOSUpgrade”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    “NoAutoUpdate”=dword:00000001
    “NoAutoRebootWithLoggedOnUsers”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\WindowsUpdate]
    “DisableOSUpgrade”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\WindowsUpdate\AU]
    “NoAutoUpdate”=dword:00000001
    “NoAutoRebootWithLoggedOnUsers”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update]
    “AUOptions”=dword:00000001

    These two confused the heck out of me. The top is the same as W 7, that’s not a problem BUT the second half has completely disappeared from any W 10.0 I have. So as indicated they must be for W 10.0 1511 or earlier. Scan your Registry for those Keys, if they line up with them, then they are for you.

    REG WU AU OSUgrade Turned Off, Au & WU Turned Off.reg (W 10.0 1511 or earlier)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    “NoAutoUpdate”=dword:00000001
    “NoAutoRebootWithLoggedOnUsers”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
    “KickoffSource”=dword:00000000
    “KickoffDownload”=dword:00000000
    “AllowOSUpgrade”=dword:00000000
    “ReservationsAllowed”=dword:00000000
    “Refresh”=dword:00000000

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade\State]

    REG WU AU OSUgrade Enabled, Au & WU Turned Off.reg (W 10.0 1511 or earlier)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
    “NoAutoUpdate”=dword:00000001
    “NoAutoRebootWithLoggedOnUsers”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
    “KickoffSource”=dword:00000001
    “KickoffDownload”=dword:00000001
    “AllowOSUpgrade”=dword:00000001
    “ReservationsAllowed”=dword:00000001
    “Refresh”=dword:00000001

    Note: The W designations: I am not sure if W 7 has added the OSUpgrade feature or not. If they haven’t there would be nothing to look at those Keys anyway so they won’t hurt anything. They weren’t there when I was on W 7, that’s all I can say….

    C&P them into a text file with ext= .reg

    Then run which ever one seems appropriate …. That’s it.

    NOW YOU ARE IN TOTAL CONTROL AND IT IS YOUR RESPONSIBILITY TO CHECK FOR PATCHES, DOWNLOAD AND IN INSTALL THEM!

    I only use the WU GUI on W 10 only when I want to Download an Upgrade, otherwise I never touch it.

    I use Powershell for all other WU activity….

    Powershell ISE Module: Installing PSWindowsUpdate, Script: Provisioning Get-PendReboot

    Windows 10 is even more complicated if one is complete about it but the above is the minimum.

    Additional Windows 10 Registry Adjustment and Controls

    Windows Update Unified Update Platform

    Windows 10 UUP is quite interesting and deserves some review rather than just a brush off!
    That is a very profound statement, coming from somebody whom doesn’t like anything or anybody messing with her EDS’s. They are invaluable for Recovery purposes, In Place Updates for repair purposes(All Data an Apps are left in place BUT Backup, Backup, Backup), as well as a potential clean install which I have literally not done since W 7.
    I have successful completed both UUP on and UUP off.

    UUP off is what I do first, so that I get my coveted C:\$Windows~BT\Source\Install.ESD. (Don’t forget to copy it to another Directory)
    As usual a clean up was in order to circumvent the ‘Reboot Install’ then a REBOOT was done.
    Then I needed to do a complete and thorough Deep Clean Up.
    I then Run the Registry Script Below!
    Reboot again.

    I then Clicked the Windows GUI Update Button, and the Download began again, only this time I was getting a Delta download into the %WinDir%\”SoftwareDistrabution\Download” Directory.
    DO NOT REBOOT YET!

    UUP to ISO – Create Bootable ISO from Windows 10 Build Upgrade Files – Windows 10 Tutorials

    FOLLOW THOSE INSTRUCTIONS EXPLICITLY, any deviation will result in failure.
    They will give you a DELTA ISO. Inside that ISO in the Source Directory is a DELTA Install.WIM. It is not acceptable for Recovery OR ‘In Place Update’ of your whole Image.
    (in other words it is less than what you need).
    Clean Up again and only then do you do a Restart. I also Turned OFF UUP before the Restart but you can suite yourself when you do that.

    I than Run the Delta ISO and Upgraded that way. I have don’t this procedure this way once. but there is noway it should not be Repeatable.

    NOTE: I make an ISO out of the FIRST/Complete ESD. I may cover that later. I am a bit reticent to do that because I don’t have a WebSite to point you to like UUP to ISO. Many of you probably have your own process that you do that with as well. If somebody is interested in doing a Tools Page for that, Please feel free to do so!

    REG WU UUP Windows Update Unified Update Platform – OFF Registy W 10.0.14971.1000 & Grter.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate]
    “SupportsUUP”=dword:00000000

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator]
    “EnableUUPScan”=dword:00000000

    REG WU UUP Windows Update Unified Update Platform – ON Registy W 10.0.14971.1000 & Grter.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate]
    “SupportsUUP”=dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator]
    “EnableUUPScan”=dword:00000001

    REG WU CloudContent – Disable Windows Consumer Features.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent]
    “DisableWindowsConsumerFeatures”=dword:00000001

    REG WU DO Windows Update Delivery Optimization Set ByPass 100 W 10.0.14986.1001 & Grter(Some Earlier).reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\DeliveryOptimization]
    “DODownloadMode”=dword:00000064

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization]
    “DODownloadMode”=dword:00000064

    REG UPDATE Device Allow MU Update Service On.reg (I have this for a bit of extra assurance. It is more complete than WU. Now MS sets MU as primary on W 8,1 and W 10(?maybe on W 7 as well?) You can check this in Service Manager.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update]
    “AllowMUUpdateService”=dword:00000001

    REG POLICY Manager AllowCortana Experience OFF.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Experience\AllowCortana]
    “value”=dword:00000000

    REG MPEngine Windows Defender Enable protection against adware on Windows 10.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\MpEngine]
    “MpEnablePus”=dword:00000001

    REG LongPathsEnabled 14352.1002 – System, System File – Enable NTFS Long Paths.reg

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies]
    “LongPathsEnabled”=dword:00000001

    Add to Right Click Menu.reg (Acceptable for W 7 or greater)

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\CABFolder\Shell\RunAs]
    @=”Install .cab or .msu update”
    “HasLUAShield”=””

    [HKEY_CLASSES_ROOT\CABFolder\Shell\RunAs\Command]
    @=”cmd /k dism /online /add-package /packagepath:\”%1\””

    Remove From Right Click Menu.reg

    Windows Registry Editor Version 5.00

    [-HKEY_CLASSES_ROOT\CABFolder\Shell\RunAs]

    --------------------------------------

    1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

    SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

    CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
    Graphics Radeon RX 580, RX 580 ONLY Over Clocked
    More perishable

    2xMonitors Asus DVI, Sony 55" UHD TV HDMI

    1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
    1xOS W8.1 Pro, NAS Dependent, Same Sony above.

    -----------------

    2 users thanked author for this post.
    Viewing 3 reply threads
    Author
    Replies
    • #97145

      Some of the “lost” GPO settings for 1607 Pro look like they can be set via these keys.  I have begun testing on a domain controller to see if pushing direct REG keys to clients can overcome the intentional limitations on GP.

      I’ll try to remember to post results here – might be a few days.

      ~ Group "Weekend" ~

      • #97162

        While those keys changing (not tuning) intended behaviour may be experimented on personal machines, I don’t see it as good practice to push them to supported clients.
        But each environment is different 🙂

        • #97317

          This is why we test GPO settings and reg key pushes to client workstations from the DC before live deployment.  🙂

          Yes there can be unexpected side effects from indiscriminate use of GPO on a domain, but this feature gives us a rich management ability to set custom aspects that our clients want and need, as well as the ability to lock down certain vulnerabilities that expose clients to malware (as only one part of a multi-part approach to malware mitigation.)

          We use GPO to turn off features we don’t want on the corporate network, turn on features in a consistent manner, set certain defaults so all users only have to learn one method, create file share mappings, push shared printer drivers to every user with presets that make sense for their work process (this last is especially helpful with plotters and loaded paper role types, sizes, color quality settings etc.)

          This greatly reduces the time needed to setup a new user profile, or a new machine, and makes it very easy to push out new devices to every machine (like a printer upgrade or a new share.)

          We also use it to turn off AutoPlay and in some cases restrict USB usage to authorized use (on compatible hardware.)

          Just a few of the many uses we find for GPO on a large network.

          ~ Group "Weekend" ~

          • #97340

            You can always rollback the changes to registry pushed by GPP by implementing the previous values or deleting the values/keys created, if you always keep current documentation about the changes.
            As in all those types of implementations, a little bit of “feel” for how Windows works and experience with previous behaviour helps a lot in making the right decisions.

            I completely agree with the types of customisations which you listed. My comments were targeted to emulating other versions of Windows than the one in use by disabling Cortana or other features where this is not supported natively by the OS in use. This can be acceptable in a home user setup or test environment, but when deployed to a larger number of users, it creates problems in maintaining them, while the licensing considerations might be another issue.

    • #97198

      While those keys changing (not tuning) intended behaviour may be experimented on personal machines, I don’t see it as good practice to push them to supported clients.
      But each environment is different  🙂

      That is probably what the are counting on. WSUS and SCCM probable control them though.

      --------------------------------------

      1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

      SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

      CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
      Graphics Radeon RX 580, RX 580 ONLY Over Clocked
      More perishable

      2xMonitors Asus DVI, Sony 55" UHD TV HDMI

      1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
      1xOS W8.1 Pro, NAS Dependent, Same Sony above.

      -----------------

      • #97207

        WSUS is a Windows/Microsoft Update internal server which has the same functionality like Windows/Microsoft Update for end-users. SCCM include WSUS and has in addition deployment and inventory capabilities and some management features implemented via Local Group Policy. It uses an agent installed on the managed machines for this purpose.
        The registry keys can be pushed via Group Policy Preference, an Active Directory mechanism.
        My point was that whoever uses Active Directory and administers managed environments should not use registry keys to hack/modify built-in functionality, but use the suitable product for the purpose, which is either Enterprise version or in many instances and in particular for smaller businesses, Pro is an acceptable alternative.
        Registry keys changes should be used only for fine-tuning the product, but not for implementing in Pro functionality which is available only in Enterprise, because this is not guaranteed to work in the future and there would be no warning or documentation about such functionality change.

        • #97318

          Registry keys changes should be used only for fine-tuning the product, but not for implementing in Pro functionality which is available only in Enterprise, because this is not guaranteed to work in the future and there would be no warning or documentation about such functionality change.

           

          This is my fear as well, which is why I would wish that the lost functionality in Pro be restored.  In particular relating to updates ( which horse I have beat to death by now, to no avail.)  WSUS has it’s own high maintenance needs – the care and feeding of WSUS is not trivial and it’s definitely not “set and forget.”  But even so, that’s preferable to the mess that un-managed patching can do to a critical system.

          We do push some reg keys out, but generally only for older – stable – features.  But even then it requires more babysitting over time, and yes – it’s happened that a patch will break our settings.

          MS supported GPO settings are by far the preferred method for long term use.

           

          ~ Group "Weekend" ~

          • #97343

            WSUS looks complicated at first and definitely require effort to configure, but I found that after its behaviour is understood well, the effort to maintain it effectively is not huge.
            Maybe we should create thread here and clarify WSUS if there is enough interest about it, although there are only a few of us who deal with this sort of small to medium size enterprise approach.
            I should mention here that anyone with enough interest can set up WSUS as a role of Windows Server 180-days free trial from Microsoft.
            https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2012-r2
            https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016/
            https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016-essentials

            What I found highly useful for Windows 10 updating is to configure DO to the value Bypass (100) and use full update files (not Express). This approach never failed me, at least since November 2016 on 1607, any distribution (10 Pro, 10 Enteprise, Server 2016).

            Microsoft seems to work on something big in relation to fixing DO and Windows Creators Edition, also possible in relation to the new CU mechanism for Windows 7/8.1.
            This explains what we have seen in February 2017 and to less extent January 2017.
            So what I said before about not using Express files and setting DO on Bypass may become (hopefully) obsolete in the next few weeks.

          • #97364

            OKAY Gentlemen,

            I am not exactly sure which Registry settings you are specifically looking at but I just realized I have a compilation error in the supportive Document Link department and for that I apologize. This is not an excuse but there is so much to pull together, some gets lost in the cracks. I do endeavor to be as complete as possible. It is mentioned in one other post that I did but missed here.

            KB939844 Configure Automatic Updates using Registry Editor
            https://technet.microsoft.com/en-us/library/dd939844(v=ws.10).aspx

            Even though this was last updated in 2011 it was current when I started using it on W 7, and I have no reason to believe that, that is still not the case. The bottom section is for the “Client” side. If one sets the other keys as I do, “AUOption” would automatically be set to ‘1’ by the system up to W 8.1. If you look at “AUOption” the Range is 2-4. ‘1’ is AU off as I said set by the system. In W 10.0 1607 they have started to letting it float, so I am setting to ‘1’ for the system.

            The new one in W 8.1 is about OS Upgrade in it various “Names/values”. It is also in W 10.0, like that too.

            There maybe even other thing that should be include, that I as yet haven’t come across.
            Please let us know.

            NOTE: I will see if Kirsty will mind inserting it in the main post.
            EDIT: #96121 has now been edited

            --------------------------------------

            1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

            SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

            CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
            Graphics Radeon RX 580, RX 580 ONLY Over Clocked
            More perishable

            2xMonitors Asus DVI, Sony 55" UHD TV HDMI

            1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
            1xOS W8.1 Pro, NAS Dependent, Same Sony above.

            -----------------

      • #97215

        CH 100,

        My point is this, those services are supposed to take control and manage a client PC. They must use a similar system as well as GPO.

        My PC’s are Managed as well, by ME, not by MS. Those Registry Adjustments is how I manage MY PC.
        That is the Long and the Short of it! I will also Fight MS tooth and thog to KEEP Control of my PC. MS doesn’t own or pay for it I DID. I have been on this road for years and I am not getting off of it anytime soon!

        --------------------------------------

        1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

        SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

        CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
        Graphics Radeon RX 580, RX 580 ONLY Over Clocked
        More perishable

        2xMonitors Asus DVI, Sony 55" UHD TV HDMI

        1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
        1xOS W8.1 Pro, NAS Dependent, Same Sony above.

        -----------------

    • #97199

      Some of the “lost” GPO settings for 1607 Pro look like they can be set via these keys. I have begun testing on a domain controller to see if pushing direct REG keys to clients can overcome the intentional limitations on GP.

      I’ll try to remember to post results here – might be a few days.

      That’s why I try to stay away form GPO and turn to the Registry.

      --------------------------------------

      1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

      SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

      CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
      Graphics Radeon RX 580, RX 580 ONLY Over Clocked
      More perishable

      2xMonitors Asus DVI, Sony 55" UHD TV HDMI

      1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
      1xOS W8.1 Pro, NAS Dependent, Same Sony above.

      -----------------

      • #97328

        While direct REG key modification is very powerful, the problem is that they are often unsupported and can be (as you recently discovered) a moving target.

        I do use them from time to time, and am currently investigating the suggestions you gave in the Tools forum.  But whenever possible, I much prefer GPO for my large client networks.  It’s generally stable for long term use, it’s supported by Microsoft (which is important to us), and we don’t have to worry as much about slight differences in the client versions and patch status.

        Also I saw earlier a question by you about the long term survival of GPO.  I can tell you with a very high level of confidence that – at least on SMB and ENT domains – Group Policy is alive and doing well.  It will be so for the foreseeable future under Server 2012 R2 and Server 2016 and beyond. And even though it’s a bit less than it used to be, local GP on Windows 10 Pro in stand alone or peer to peer mode will also be around for the foreseeable future.

         

        ~ Group "Weekend" ~

        • #97335

          😀 😆 Hey wait just hang dang minute HERE! LMFAO 😆 A moving target you say??? When has Microsoft NOT been a movin’ target, I give you the last 2 1/2 year as an example. 😆

          However, since we on the subject, in all seriousness I hear people here, on this post and other places, mention ‘guaranties’, where has there been any ‘guaranties’ in tech? Even if they display them, put them in a EULA’s or say them, they are rarely kept. What can one do, ‘well take me to court’, some ‘guaranty’. It costs one more to make them live up to it, for you, if you are successful, then it is worth. If I have learned anything in life to date is, there are very, very few ‘guaranties’.

          --------------------------------------

          1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

          SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

          CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
          Graphics Radeon RX 580, RX 580 ONLY Over Clocked
          More perishable

          2xMonitors Asus DVI, Sony 55" UHD TV HDMI

          1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
          1xOS W8.1 Pro, NAS Dependent, Same Sony above.

          -----------------

          1 user thanked author for this post.
          • #97344

            Crysta, just to clarify for everyone else who might read and not understand the latest few posts here.
            While you write about YOUR computers, NetDef and me are exchanging ideas about managed environments with tens, hundreds, maybe thousands of users. The approach in those environments is completely different and any change can get easily out of hand if not managed well, but at the same time we are trying to filter out what is applicable to those environments from your proposed settings for tuning the OS.

            1 user thanked author for this post.
          • #97348

            Fair enough but surely if an “Enterprise” of so many computer is needing/trying  to Manage them with out the Usual AD, WSUS or SCCM, in my humble opinion, they’re on a fools errand.

            I don’t believe I have posted anything here for that kind of environment, unless it is a Mobile computer of some sort that is outside of some or all of those services, then maybe.

            Another thing why would such large Corps try to get away with “Pro” PC’s anyway????

            As far as Unsupported Adjustments, Enterprises, Companies, and maybe Businesses often do them whether it is for internal only or Both. My examples are in the news and other places. At the end of the day, most are loathed to let MS push them around…. (Yeah, I no that sometimes things break, OH, well)

            --------------------------------------

            1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

            SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

            CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
            Graphics Radeon RX 580, RX 580 ONLY Over Clocked
            More perishable

            2xMonitors Asus DVI, Sony 55" UHD TV HDMI

            1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
            1xOS W8.1 Pro, NAS Dependent, Same Sony above.

            -----------------

            • #97572

              Some of my clients are very small:  5 to 10 users/workstations and a single server running everything network.  These are the SMB’s that have relied for years on the ‘Pro” edition to meet their needs.  I’m researching how to best support Windows 10 Pro for them.  There are – as you and others here have helped identify . . . some odd issues.  They are also the companies that have the hardest time justifying budget for a recurring cost subscription.  (Recurring costs are the bane of variable – and often slim – budgets for most SMB’s.)

              Some are . . . larger.  For them running Enterprise is not a problem, and the support/management tools I need to do justice for them work nicely in Win10ENT.

              And a shout-out to both of you:  knowingly or not this discussion has produced some positive results.  Thanks!  🙂

              ~ Group "Weekend" ~

              2 users thanked author for this post.
            • #97616

              Just for the record, that is what I thought you were talking mostly about very small to smaller SMB’s. As you pointed out, even SMB’s can get to the larger size but I would think 100 seats would come close to maxing out the SMB concept.

              On your smallest ones you might be able to do some of the Management type Registry adjustment but I agree with CH 100 the more seats you have at a location the more problematic it ?COULD? get. If one does not have some “Management” Servers for the ‘PC’ to hide behind what is an Admin to do??? Leave things up to MS and there shenanigans??? I have admit I would rather rely on myself then MS, BUT Document, Document, Document, Document. Of course it should go with out saying, Date must be kept thoroughly backed up, on and off site.

              Here is something more aimed directly at SMB’s. I am a Synology customer, having 3 singles, I was reading in their Newsletter that they are getting into AD. If they are getting into that kind of Management then maybe they are think about going further. The only thing I would be careful to checkout is the Processing power of the box when getting to far beyond NAS functions. I would love to have a 5 bay with 10 TB spinning rust and augmented by SSD’s. They are getting to that additional server capacity though.

              Your most welcome that is what it is all about here. No one person has all the answers and we all bring different backgrounds to the table.

              --------------------------------------

              1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

              SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

              CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
              Graphics Radeon RX 580, RX 580 ONLY Over Clocked
              More perishable

              2xMonitors Asus DVI, Sony 55" UHD TV HDMI

              1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
              1xOS W8.1 Pro, NAS Dependent, Same Sony above.

              -----------------

    • #97200

      I have found some erroneousness has crept into my W 10.0 1607 and later Builds that I didn’t fully realize until today. A whole Key has gone MIA and now the Registry Adjustment for W 10.0 14303.0 and Later and W 8.1 are exactly the same. The wheel has come full circle.

      I am preparing an Email to Kirsty, for her to help me clean up the Post… Stay tuned. 😀

      EDIT: #96121 now edited 🙂

      --------------------------------------

      1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

      SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

      CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
      Graphics Radeon RX 580, RX 580 ONLY Over Clocked
      More perishable

      2xMonitors Asus DVI, Sony 55" UHD TV HDMI

      1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
      1xOS W8.1 Pro, NAS Dependent, Same Sony above.

      -----------------

      1 user thanked author for this post.
    Viewing 3 reply threads
    Reply To: Registry Adjustments for ALL, W 7, W 8.1 and W 10

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: