Classic Shell 4.3.1 was just released

Page 3 of 3 FirstFirst 123
  1. prikker's Avatar
    Posts : 382
    Windows 10 Home
       #21

    @dalchina: A problem with this package. Error code 2503. I reinstalled it, but as administrator. Now it installed without a problem.
      My Computer

  2. dalchina's Avatar
    Posts : 29,927
    Win 10 Pro (1903)
       #22

    Thanks, but still the same problem.

    Ivo (author) commented:
    Try downloading again. I accidentally used the old certificate (the same as 4.3.0) instead of the new one.
    It is also possible your problem is related to smart screen or other heuristic that is naturally suspicious of new and unknown software.
      My Computers

  3. dalchina's Avatar
    Posts : 29,927
    Win 10 Pro (1903)
       #23

    Hi, on Classic Shell forum they suggest this - @Josey Wales - I wonder if you could zip these registry keys and post them so I can compare? (No other Win 10 PC's). Thanks.

    Solution to The System Administrator Has Set Policies to Prevent - Microsoft Community

    I'd been looking through some older posts based on the error message and it seemed on key they referred to isn't present.

    But the oddity is I don't have problems installing anything else that I know of - just this version. I've tried a few msi's and they run ok.

    I have enabled installation logging - this is the log- never having looked at these, I'd appreciated any suggestions:
    === Verbose logging started: 14/08/17 06:55:08 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\SysWOW64\msiexec.exe ===
    MSI (c) (F4:74) [06:55:08:995]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (F4:74) [06:55:08:995]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (F4:E8) [06:55:09:057]: Resetting cached policy values
    MSI (c) (F4:E8) [06:55:09:057]: Machine policy value 'Debug' is 7
    MSI (c) (F4:E8) [06:55:09:057]: ******* RunEngine:
    ******* Product: C:\ProgramData\ClassicShellSetup64_4_3_1.msi
    ******* Action:
    ******* CommandLine:
    MSI (c) (F4:E8) [06:55:09:104]: Machine policy value 'DisableUserInstalls' is 0
    MSI (c) (F4:E8) [06:55:09:229]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\ProgramData\ClassicShellSetup64_4_3_1.msi' against software restriction policy
    MSI (c) (F4:E8) [06:55:09:229]: SOFTWARE RESTRICTION POLICY: C:\ProgramData\ClassicShellSetup64_4_3_1.msi has a digital signature
    MSI (c) (F4:E8) [06:55:09:932]: SOFTWARE RESTRICTION POLICY: C:\ProgramData\ClassicShellSetup64_4_3_1.msi is not permitted to run at the 'unrestricted' authorization level.
    MSI (c) (F4:E8) [06:55:09:932]: SOFTWARE RESTRICTION POLICY: The path rule '{3CBE1D05-2ADC-4572-9B07-3711C065D3CB}' with image name 'C:\ProgramData\*.msi' in the default software restriction machine policy disallows execution. The returned execution level was 0
    MSI (c) (F4:E8) [06:55:09:932]: The installation of C:\ProgramData\ClassicShellSetup64_4_3_1.msi is not permitted by software restriction policy. The Windows Installer only allows installation of unrestricted items. The authorization level returned by software restriction policy was 0x0 (status return 0x0).

    MSI (c) (F4:E8) [06:55:09:932]: Note: 1: 1718 2: C:\ProgramData\ClassicShellSetup64_4_3_1.msi
    MSI (c) (F4:E8) [06:55:09:932]: MainEngineThread is returning 1625
    === Verbose logging stopped: 14/08/17 06:55:09 ===

    ===================================================================
    By comparison 4.3.0:
    === Verbose logging started: 14/08/17 07:08:47 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\SysWOW64\msiexec.exe ===
    MSI (c) (E0:40) [07:08:47:892]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (E0:40) [07:08:47:892]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

    MSI (c) (E0:0C) [07:08:47:954]: Resetting cached policy values
    MSI (c) (E0:0C) [07:08:47:954]: Machine policy value 'Debug' is 7
    MSI (c) (E0:0C) [07:08:47:954]: ******* RunEngine:
    ******* Product: C:\ProgramData\ClassicShellSetup64_4_3_0.msi
    ******* Action:
    ******* CommandLine:
    MSI (c) (E0:0C) [07:08:48:001]: Machine policy value 'DisableUserInstalls' is 0
    MSI (c) (E0:0C) [07:08:49:048]: Cloaking enabled.
    MSI (c) (E0:0C) [07:08:49:048]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (E0:0C) [07:08:49:048]: End dialog not enabled
    MSI (c) (E0:0C) [07:08:49:048]: Original package ==> C:\ProgramData\ClassicShellSetup64_4_3_0.msi
    MSI (c) (E0:0C) [07:08:49:048]: Package we're running from ==> C:\Windows\Installer\73966d.msi
    MSI (c) (E0:0C) [07:08:49:064]: APPCOMPAT: Uninstall Flags override found.
    MSI (c) (E0:0C) [07:08:49:064]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (c) (E0:0C) [07:08:49:064]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (c) (E0:0C) [07:08:49:064]: APPCOMPAT: looking for appcompat database entry with ProductCode '{383BB30A-B4A7-4666-9A83-22CFA8640097}'.
    MSI (c) (E0:0C) [07:08:49:064]: APPCOMPAT: no matching ProductCode found in database.
    MSI (c) (E0:0C) [07:08:49:423]: MSCOREE not loaded loading copy from system32
    MSI (c) (E0:0C) [07:08:49:470]: Machine policy value 'DisablePatch' is 0
    MSI (c) (E0:0C) [07:08:49:470]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (c) (E0:0C) [07:08:49:470]: Machine policy value 'DisableMsi' is 0
    MSI (c) (E0:0C) [07:08:49:470]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (c) (E0:0C) [07:08:49:470]: User policy value 'AlwaysInstallElevated' is 0
    MSI (c) (E0:0C) [07:08:49:470]: Product {383BB30A-B4A7-4666-9A83-22CFA8640097} is admin assigned: LocalSystem owns the publish key.
    MSI (c) (E0:0C) [07:08:49:470]: Product {383BB30A-B4A7-4666-9A83-22CFA8640097} is managed.
    MSI (c) (E0:0C) [07:08:49:470]: Running product '{383BB30A-B4A7-4666-9A83-22CFA8640097}' with elevated privileges: Product is assigned.
    MSI (c) (E0:0C) [07:08:49:470]: Machine policy value 'DisableLUAPatching' is 0
    MSI (c) (E0:0C) [07:08:49:470]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (c) (E0:0C) [07:08:49:470]: APPCOMPAT: looking for appcompat database entry with ProductCode '{383BB30A-B4A7-4666-9A83-22CFA8640097}'.
    MSI (c) (E0:0C) [07:08:49:470]: APPCOMPAT: no matching ProductCode found in database.
    MSI (c) (E0:0C) [07:08:49:470]: Transforms are not secure.
    MSI (c) (E0:0C) [07:08:49:470]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\David\AppData\Local\Temp\MSI577db.LOG'.
    MSI (c) (E0:0C) [07:08:49:470]: Command Line: CURRENTDIRECTORY=E:\Downloads CLIENTUILEVEL=0 CLIENTPROCESSID=16352
    MSI (c) (E0:0C) [07:08:49:470]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{5DF2A896-2547-4DAB-B4C5-53AA5E21A689}'.
    Last edited by dalchina; 14 Aug 2017 at 01:10.
      My Computers

  4. Steve C's Avatar
    Posts : 6,286
    Windows 10 Pro 64 bit
       #24

    I use Classic shell on all PCs currently running the AU. I just installed CS from Classic Shell - Start menu and other Windows enhancements and it it installed fine and runs fine on all PCs.
      My Computers

  5. dalchina's Avatar
    Posts : 29,927
    Win 10 Pro (1903)
       #25

    Excellent... I'm hoping to find a way to achieve the same.. any clues?

    ** I have snatched a copy of the msi file from C:\ProgramData\ClassicShellSetup64_4_3_1.msi and copied it to my desktop.

    This msi runs ok.

    The install log shows that for this version
    SOFTWARE RESTRICTION POLICY: The path rule '{3CBE1D05-2ADC-4572-9B07-3711C065D3CB}' with image name 'C:\ProgramData\*.msi' in the default software restriction machine policy disallows execution.

    Now note that is *.msi

    This seems puzzling, as v4.3.0 also creates
    C:\ProgramData\ClassicShellSetup64_4_3_0.msi

    Purely on the basis of the two logs, it is not clear to me why one is restricted, but the other not.

    Identifying this by searching the registry for
    3CBE1D05-2ADC-4572-9B07-3711C065D3CB

    gives this:
    Classic Shell 4.3.1 was just released-1.jpg

    - so the restriction is applied by an anti-ransomware program, Cryptoprevent.

    I still don't understand why this only affects v4.3.1 and not v4.3.0.
    Last edited by dalchina; 14 Aug 2017 at 08:00.
      My Computers

  6. Gordon7's Avatar
    Posts : 182
    Win 10 rs1 - build 14393.1944
       #26

    dalchina try to whitelist ClassicStartMenu 4.31 in CryptoPrevent and reboot!

    Then reinstall CSM.
      My Computer

  7. dalchina's Avatar
    Posts : 29,927
    Win 10 Pro (1903)
       #27

    Already installed, thanks.
      My Computers


 
Page 3 of 3 FirstFirst 123

  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 21:51.
Find Us




Windows 10 Forums