KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider

Page 55 of 102 FirstFirst ... 545535455565765 ... LastLast

  1. Posts : 1,476
    Windows 10 Pro 64bit 20H2 19042.844
       #540

    In the Future Plan on Getting Me a Samsung 250GB SSD for my I7 Desktop!!, But for now my Western Digital 250GB SSD handles fine for my needs, that was budget purchase when I was using my AMD FX system lol, transferred the newer SSD to this PC

    As for 1803 Install, working great thus far, now just have to hope last PC #4 works fine too when I do that install, may wait til officially out for that one lol
      My Computers


  2. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #541

    pauliewog said:
    I'm glad too bud believe me! lol I don't know why windows does this but I never had any issues like this on an upgrade before or in fact for a long time.
    Have you been in the Insider Program during development of RS4? I have and it was a nightmare for me since first build. A few builds worked fine in between but then it all went back to square one. Build 17133.1 works surprisingly well considering what was going on during the journey to this point. :)

    Some insiders had pretty much no issues at all, except for some minor software glitches.
      My Computers


  3. Posts : 2,832
    Windows 10 Pro X64
       #542

    Hi,

    It seems as if every new version of Windows 10 brings that good old Event ID 1016 back again.
    A rather innocent DCOM error but annoying to those like you and me who'd rather not see too many errors if it can be helped.

    Fortunately there's an easy way to get rid of it regardless to what app it points to without digging into the registry and DCOMcnfg for that matter.

    Open Powershell Admin, paste in the code below, let it run and reboot the machine:

    Code:
    function enable-privilege
    { param(
     ## The privilege to adjust. This set is taken from http://msdn.microsoft.com/en-us/libr...16(VS.85).aspx
      [ValidateSet(
     "SeAssignPrimaryTokenPrivilege", "SeAuditPrivilege", "SeBackupPrivilege", "SeChangeNotifyPrivilege", "SeCreateGlobalPrivilege",
     "SeCreatePagefilePrivilege", "SeCreatePermanentPrivilege", "SeCreateSymbolicLinkPrivilege", "SeCreateTokenPrivilege",
     "SeDebugPrivilege", "SeEnableDelegationPrivilege", "SeImpersonatePrivilege", "SeIncreaseBasePriorityPrivilege",
     "SeIncreaseQuotaPrivilege", "SeIncreaseWorkingSetPrivilege", "SeLoadDriverPrivilege", "SeLockMemoryPrivilege",
     "SeMachineAccountPrivilege", "SeManageVolumePrivilege", "SeProfileSingleProcessPrivilege", "SeRelabelPrivilege",
     "SeRemoteShutdownPrivilege", "SeRestorePrivilege", "SeSecurityPrivilege", "SeShutdownPrivilege", "SeSyncAgentPrivilege",
     "SeSystemEnvironmentPrivilege", "SeSystemProfilePrivilege", "SeSystemtimePrivilege", "SeTakeOwnershipPrivilege", "SeTcbPrivilege",
     "SeTimeZonePrivilege", "SeTrustedCredManAccessPrivilege", "SeUndockPrivilege", "SeUnsolicitedInputPrivilege")]
     $Privilege,
     ## The process on which to adjust the privilege. Defaults to the current process.
     $ProcessId = $pid,
     ## Switch to disable the privilege, rather than enable it.
     [Switch] $Disable
     )
     ## Taken from P/Invoke.NET with minor adjustments.
     $definition = @'
     using System;
     using System.Runtime.InteropServices;
      
     public class AdjPriv
     {
      [DllImport("advapi32.dll", ExactSpelling = true, SetLastError = true)]
      internal static extern bool AdjustTokenPrivileges(IntPtr htok, bool disall,
       ref TokPriv1Luid newst, int len, IntPtr prev, IntPtr relen);
      
      [DllImport("advapi32.dll", ExactSpelling = true, SetLastError = true)]
      internal static extern bool OpenProcessToken(IntPtr h, int acc, ref IntPtr phtok);
      [DllImport("advapi32.dll", SetLastError = true)]
      internal static extern bool LookupPrivilegeValue(string host, string name, ref long pluid);
      [StructLayout(LayoutKind.Sequential, Pack = 1)]
      internal struct TokPriv1Luid
      {
       public int Count;
       public long Luid;
       public int Attr;
      }
      
      internal const int SE_PRIVILEGE_ENABLED = 0x00000002;
      internal const int SE_PRIVILEGE_DISABLED = 0x00000000;
      internal const int TOKEN_QUERY = 0x00000008;
      internal const int TOKEN_ADJUST_PRIVILEGES = 0x00000020;
      public static bool EnablePrivilege(long processHandle, string privilege, bool disable)
      {
       bool retVal;
       TokPriv1Luid tp;
       IntPtr hproc = new IntPtr(processHandle);
       IntPtr htok = IntPtr.Zero;
       retVal = OpenProcessToken(hproc, TOKEN_ADJUST_PRIVILEGES | TOKEN_QUERY, ref htok);
       tp.Count = 1;
       tp.Luid = 0;
       if(disable)
       {
        tp.Attr = SE_PRIVILEGE_DISABLED;
       }
       else
       {
        tp.Attr = SE_PRIVILEGE_ENABLED;
       }
       retVal = LookupPrivilegeValue(null, privilege, ref tp.Luid);
       retVal = AdjustTokenPrivileges(htok, false, ref tp, 0, IntPtr.Zero, IntPtr.Zero);
       return retVal;
      }
     }
    '@
     $processHandle = (Get-Process -id $ProcessId).Handle
     $type = Add-Type $definition -PassThru
     $type[0]::EnablePrivilege($processHandle, $Privilege, $Disable)
    }
    #------------------------------------------------------------------------------------------------------------------------------------------------------
    function Takeown-Registry($key) 
    { switch ($key.split('\')[0])
     { "HKEY_CLASSES_ROOT" 
      { $reg = [Microsoft.Win32.Registry]::ClassesRoot
       $key = $key.substring(18)
      }
            "HKEY_CURRENT_USER"
      { $reg = [Microsoft.Win32.Registry]::CurrentUser
       $key = $key.substring(18)
      }
      "HKEY_LOCAL_MACHINE"
      { $reg = [Microsoft.Win32.Registry]::LocalMachine
       $key = $key.substring(19)
      }
     }
     # take ownership
     $key = $reg.OpenSubKey($key, "ReadWriteSubTree", "TakeOwnership")
     $owner = [Security.Principal.NTAccount]"Administrators"
     $acl = $key.GetAccessControl()
     $acl.SetOwner($owner)
     $key.SetAccessControl($acl)
     # set FullControl
     $acl = $key.GetAccessControl()
     $rule = New-Object System.Security.AccessControl.RegistryAccessRule("Administrators", "FullControl", "Allow")
     $acl.SetAccessRule($rule)
     $key.SetAccessControl($acl)
     
     # reset owner
     $owner = [Security.Principal.NTAccount]"NT SERVICE\TrustedInstaller"
     $acl = $key.GetAccessControl()
     $acl.SetOwner($owner)
     $key.SetAccessControl($acl)
    }
    #------------------------------------------------------------------------------------------------------------------------------------------------------
    # Grant authority to registry key
    Write-Host; Write-Host "Elevating privileges for this process" -f yellow; Write-Host
    do {$result = enable-privilege SeTakeOwnershipPrivilege } 
    until ($result -eq $true)
    do {$result = enable-privilege SeRestorePrivilege } 
    until ($result -eq $true)
    $key="HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}"
    Write-Host "Granting authority to $key"
    Takeown-Registry($key)
    $key="HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}"
    Write-Host "Granting authority to $key"
    Takeown-Registry($key)
    Write-Host; Write-Host "Done"; Write-Host
    Sometimes when Fast StartUp is active it won't work first time around. Disable it momentarily and rerun the script, it should work.

    Cheers,
      My Computers


  4. Posts : 15,426
    Windows10
       #543

    slicendice said:
    Have you been in the Insider Program during development of RS4? I have and it was a nightmare for me since first build. A few builds worked fine in between but then it all went back to square one. Build 17133.1 works surprisingly well considering what was going on during the journey to this point. :)

    Some insiders had pretty much no issues at all, except for some minor software glitches.
    I have had issues clean installing with recent builds but could upgrade.

    In desperation, I booted from a Macrium Reflect Free Home (not Free version) Rescue Drive previously created on pc, so I know it had working drivers for pc.

    I then used the Macrium Redeploy option which is used to boot Windows on dissimilar hardware (it sorts out drivers for you), and first thing it did was use the AMD Sata controller rather than the default MS Sata Controller, and BAM - windows booted fine into oobe.

    On previous installs, I always had to install the AMD sata controller afterwards, or else it would not see my hdd in the optical drive caddy. Also I would have to install bluetooth drivers etc, and one other which I forget at the moment.

    The Macrium Reflect Redeploy option just sorted out drivers in less than 20 seconds! PC booted with amd controller, bluetooth etc all perfectly working.

    I always loved Macrium Reflect Home but if it was a woman, I would ask it to marry me now :-D
      My Computer


  5. Posts : 2,832
    Windows 10 Pro X64
       #544

    Hi,

    I always loved Macrium Reflect Honme but if it was a woman, I would ask it to marry me now :-D
    Two pieces of British made software I absolutely adore: ImgBurn and Macrium Reflect.

    That plus if Steve Gibson would have written an OS it would have fitted into my pocket....

    Cheers,
      My Computers


  6. Posts : 504
    Win10 20236.1000 64bit Pro and Win7 SP1 Ultimate
       #545

    I downloaded 1803 Build 17133 using Kari's UUPDump and UUPtoISO TUT and it worked fine on my Fall Creator's Update so I'm now running the Spring Creator's Update.

    WEK
      My Computers


  7. Posts : 92
    Windows 10 Pro v21H1 Build 19043
       #546

    I upgraded to Windows 10 Pro v1803 build 17128 from v1709 build 16299.xx as an Insider a couple of weeks ago then to build 17133.1 a few days later when I found out it was rumoured to be the final release version.

    So far, it appears to be working exactly as before with almost all of my settings and games copied over, requiring me only to do a few minor tweaks and add Firewall exclusives, etc, the first time they were run. Windows has also been 100% stable with no unusual crashes or anything of that kind plus sfc /scannow and dism /online /cleanup-image /scanhealth all report a clean bill of health.

    However, I have come across a few issues which may be bugs with this build or 'hiccups' as a result of doing an upgrade rather than a clean install (my PC was built in June 2013 when Windows 8 was installed clean on it and since then I've only done in-place upgrades to the current build of Windows 10 I am using now).

    These issues are:

    1. The Recovery partition shows as an almost full drive with the letter O in File Explorer. Previous versions of Windows 10 kept this hidden. Computer Management shows this 452 MB drive but the options to unassign the drive letter and those hide it is greyed out and unselectable.

    2. Cortana displays obviously missing text that is only visible when mousing-over when I left click in the search bar without typing anything in as discussed here: Windows 10 Pro v1803 Cortana Text Visibility Issue - Windows 10 Forums

    3. I am unable to access Settings > Apps > Default apps > Set defaults by apps as the window opens then closes after a few seconds with an Event log entry pointing to an error with Ntdll.dll, a system file. The other two Choose by options, however, work fine so it is odd that doesn't. I only came across it when I was trying to find out why web pages from Cortana's search box were opening in Internet Explorer of all things rather than Edge (which is the default browser on my system).

    I may do an in-place upgrade using the ISO from a USB stick once the Media Creation Tool is released that will download this build of Windows as this has fixed similar issues to this in the past.
    Last edited by Daz1967; 09 Apr 2018 at 14:33.
      My Computer


  8. Posts : 31,398
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #547

    Daz1967 said:
    1. The Recovery partition shows as an almost full drive with the letter O in File Explorer. Previous versions of Windows 10 kept this hidden. Computer Management shows this 452 MB drive but the options to unassign the drive letter and those hide it is greyed out and unselectable.
    This has been reported before as an occasional problem with any build, so it's probably not 1803-specific.

    For the protection of curious/naïve users, it is normal for Disk Management to grey out lots of options related to recovery partitions and the like.

    The DISKPART command has no such restrictions and should be able to remove the assigned letter.
      My Computers


  9. Posts : 4,201
    Windows 10 Pro x64 Latest RP
       #548

    information   Information
    Samsung Magician discussion moved to software forum
      My Computers


  10. Posts : 3,105
    W10 Pro + W10 Preview
       #549

    Daz1967 said:
    I upgraded to Windows 10 Pro v1803 build 17128 from v1709 build 16299.xx as an Insider a couple of weeks ago then to build 17133.1 a few days later when I found out it was rumoured to be the final release version.

    So far, it appears to be working exactly as before with almost all of my settings and games copied over, requiring me only to do a few minor tweaks and add Firewall exclusives, etc, the first time they were run. Windows has also been 100% stables with no unusual crashes or anything of that kind plus sfc /scannow and dism /online /cleanup-image /scanhealth all report a clean bill of health.

    However, I have come across a few issues which may be bugs with this build or 'hiccups' as a result of doing an upgrade rather than a clean install (my PC was built in June 2013 when Windows 8 was installed clean on it and since then I've only done in-place upgrades to the current build of Windows 10 I am using now).

    These issues are:

    2. Cortana displays obviously missing text that is only visible when mousing-over when I left click in the search bar without typing anything in as discussed here: Windows 10 Pro v1803 Cortana Text Visibility Issue - Windows 10 Forums

    3. I am unable to access Settings > Apps > Default apps > Set defaults by apps as the window opens then closes after a few seconds with an Event log entry pointing to an error with Ntdll.dll, a system file. The other two Choose by options, however, work fine so it is odd that doesn't. I only came across it when I was trying to find out why web pages from Cortana's search box were opening in Internet Explorer of all things rather than Edge (which is the default browser on my system).
    Have only ever Upgraded since Insider RS4 programme began.....certainly have not experienced either of your above quoted issues.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:47.
Find Us




Windows 10 Forums