Windows 10: Classic Shell 4.3.1 was just released

Discus and support Classic Shell 4.3.1 was just released in Windows 10 Software and Apps to solve the problem; Went right in over top 4.3.0 here. Strange. I'm sure you did, but did you download it from the link in their home page? Direct from that link:... Discussion in 'Windows 10 Software and Apps' started by Josey Wales, Aug 12, 2017.

  1. f14tomcat Win User

    Classic Shell 4.3.1 was just released

    f14tomcat, Aug 12, 2017
    #16

  2. Classic Shell 4.3.1 was just released [​IMG]
     
    Josey Wales, Aug 12, 2017
    #17
  3. dalchina New Member
    @prikker - what was the message?
     
    dalchina, Aug 12, 2017
    #18
  4. xpclient Win User

    Classic Shell 4.3.1 was just released

    Auto update will be rolled out after a few days if there are no major bugs found. Until then it's on manual update. *Smile
     
    xpclient, Aug 12, 2017
    #19
  5. tracit99 Win User
    Thanks, that is good to know.
     
    tracit99, Aug 12, 2017
    #20
  6. prikker Win User
    @dalchina: A problem with this package. Error code 2503. I reinstalled it, but as administrator. Now it installed without a problem.
     
    prikker, Aug 12, 2017
    #21
  7. dalchina New Member
    Thanks, but still the same problem.

    Ivo (author) commented:
     
    dalchina, Aug 12, 2017
    #22
  8. dalchina New Member

    Classic Shell 4.3.1 was just released

    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}'.
     
    dalchina, Aug 13, 2017
    #23
  9. Steve C Win User
    Steve C, Aug 13, 2017
    #24
  10. dalchina New Member
    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 [​IMG]


    - 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.
     
    dalchina, Aug 13, 2017
    #25
  11. Gordon7 Win User
    dalchina try to whitelist ClassicStartMenu 4.31 in CryptoPrevent and reboot!

    Then reinstall CSM.
     
    Gordon7, Aug 13, 2017
    #26
  12. dalchina New Member
    Already installed, thanks.
     
    dalchina, Apr 5, 2018
    #27
Thema:

Classic Shell 4.3.1 was just released

Loading...
  1. Classic Shell 4.3.1 was just released - Similar Threads - Classic Shell was

  2. Classic shell

    in Windows 10 Software and Apps
    Classic shell: Sorry if this has already been answered. I just got a Windows update, and now I lost my classic shell, and I really need it. I guess the update got rid of it. When I click on the start button, it just flashes. I have a new laptop and use Edge. Any help would be appreciated....
  3. Classic shell

    in Windows 10 Support
    Classic shell: Sorry if this has already been answered. I just got a Windows update, and now I lost my classic shell, and I really need it. I guess the update got rid of it. When I click on the start button, it just flashes. I have a new laptop and use Edge. Any help would be appreciated....
  4. classic shell

    in Windows 10 Installation and Upgrade
    classic shell: what is the purpose of classic shell ? https://answers.microsoft.com/en-us/windows/forum/all/classic-shell/65de2760-eb0a-4c92-9b25-76aadb23625d
  5. Classic Shell to Classic Start

    in Windows 10 Software and Apps
    Classic Shell to Classic Start: I've used Classic Shell since I upgraded to Windows 10. It has been a lifesaver. The developer stopped supporting the program a couple of years age, but someone picked up on it and developed a fork called "Classic Start". Classic Shell is still working fine for me, but is...
  6. classic shell

    in Windows 10 Installation and Upgrade
    classic shell: 1.classic shell needs to configure itself 2. an administrator has blocked you from running this ap. I have an HP notebook and keep getting the above messages every time I use my laptop and I would like to continue to use classic shell, and have tried unsuccessfully to sort...
  7. Help with Classic Shell.

    in Windows 10 Customization
    Help with Classic Shell.: Hi guys, I've been using Classic Shell for a long time now, I believe several months if not the whole year. Yesterday, I got a major update for my system. Since then (Build 10586) there is one feature of CS that has been not working very well (I guess) and I cannot find...
  8. ANN: Classic Shell 4.2.6 beta is released

    in Windows 10 Software and Apps
    ANN: Classic Shell 4.2.6 beta is released: Classic Shell 4.2.6 beta was just released. Download it from here: http://www.fosshub.com/Classic-Shell...etup_4_2_6.exe Here’s what’s new: Improved support for Windows 10 Redstone New feature for setting the taskbar color, texture, and text color Menu animations for the...
  9. classic shell

    in Windows 10 Software and Apps
    classic shell: Well it doesn't work on W10 9975
  10. Classic Shell 4.2.1 is released

    in Windows 10 Software and Apps
    Classic Shell 4.2.1 is released: Hey, everyone. I just released a new version of Classic Shell. Here’s what’s new: Improved support for Windows 10 The start menu searches modern PC settings for Windows 8.1 and Windows 10 Added new Midnight skin with dark background Added new flat Metro skin that uses...