Jump to content

Octopuss

Member
  • Posts

    1,212
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Czech Republic

Posts posted by Octopuss

  1. In case anyone ever runs into the same problem:

    I managed to figure it out - purely accidentally.
    It turned out there IS a prerequisite to integrating this - it's called "servicing stack" and these KBs are released more or less along with the cumulative updates (sometimes like once per two CUs).
    Of course, this is not explained anywhere (the connection and dependency).

    The other catch is that when you try to integrate all this, you have to do it twice. WTF.
    So you have to mount the image, do whatever customizations you have prepared, then integrate the servicing stack, THEN unmount and save the image, AND THEN mount it again and finally integrate the large update.

    This is almost as annoying as booting into safe mode in Windows 10 compared to Windows 7.
    just-pure-WTF

  2. I'm trying to integrate the last cumulative update to my image, and it just wouldn't work, always giving me this error:

    Processing 1 of 1 - d:\install\OS\Win10 updates\windows10.0-kb4346783-x64.msu: An error occurred while expanding the .msu package into the temporary folder, C:\TEMP\026C4C10-7AE8-42D3-9B97-9E49018383DF.
     Error: 0x8007000d
    
    Error: 13
    
    The data is invalid.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    DISM log is equally useless

    2018-08-31 13:43:48, Info                  DPX    ProvideRequestedDataByFile: d:\install\OS\Win10 updates\windows10.0-kb4346783-x64.msu failed, Response file Name: ExtractFromCabInFile
    2018-08-31 13:43:48, Info                  DPX    Ended DPX phase: Apply Deltas Provided In File
    2018-08-31 13:43:48, Info                  DPX    DpxException hr=0x8007000d code=0x020201
    2018-08-31 13:43:48, Info                  DPX    Ended DPX phase: Resume and Download Job
    2018-08-31 13:43:48, Info                  DPX    DpxException hr=0x8007000d code=0x020217
    2018-08-31 13:43:48, Error                 DISM   DISM Package Manager: PID=1108 TID=4220 Failed to start the DPX job to extract MSU files. - CMsuPackage::Expand(hr:0x8007000d)
    2018-08-31 13:43:48, Error                 DISM   DISM Package Manager: PID=1108 TID=4220 Failed to expand the MSU file into temp folder C:\TEMP\026C4C10-7AE8-42D3-9B97-9E49018383DF. - CMsuPackage::Install(hr:0x8007000d)

     

    Are there any other updates I need to integrate first, or what's going on? Does anyone know?

  3. 22 hours ago, Aethelflaed said:

    In any case, those CleoDesktop themes apply just fine. I have several of them, in fact, among which a Win7 Aero theme which, I take it, is also what you downloaded.
     

    I don't really like the OldNewExplorer requirement. It's not a hard one, but without it it looks weird. I would have very much preferred if he simply left Explorer untouched.

    WSw3ccV.png

  4. Jesus, I give up. The guy is an id***. I wasted half an hour of my life trying to explain not everyone wants to install five other programs just to install a stupid theme, and he just goes

    "When OldNewExplorer not work on future, it will has update"

    Wasted money.

  5. That is weird, because I can't see any command bar in my Windows 10 at all.

    Communicating with the guy is major pain in the a**, because his engrish looks more like klingon, and I have no idea what is he saying :( I've been trying to find out whether that OldNewExplorer is a hard requirement for the theme, and his replies are always different.

  6. 11 hours ago, Aethelflaed said:

    Yes, Windows 10 supports themes of a sort, without having to patch dll files, or inject other dlls, into your system. Such themes are limited to colours, backgrounds, sounds and mouse cursors, however.

    Yet the Windows 10 engine is capable of altering much more than just the things just mentioned - buttons, titlebars, scrollbars and the like can all, in principle, be changed. Microsoft doesn't really want you to do this, preferring for its users to work with a mostly uniform interface. This is not surprising, really. The look of its interface helps Microsoft set Windows 10 aside from, for instance, Windows XP, Vista, 7, or 8. This is important from a marketing viewpoint as these OSes are otherwise very similar. Strip away Windows 'app' support, a few security features, and a lot of telemetry, and Windows 10 is not so very different from 7.

    By using Bigmuscle's dll file, or applying patches to Windows' own dll files, users can 'relax' Microsofts' restrictions, and essentially do what Microsoft does every time it launches a new version of its OS. My own Windows 10 desktop currently looks almost identical to Windows 7, as you can see from the images below (note that I've also changed the icons, and installed a start menu replacer). Others prefer more radical changes - DeviantArt is a good place to start if you are interested in Windows 'skinning'.

    Do please note that patching Windows dll files can, potentially, be risky, so always make sure that you have proper backups and the means to recover your system should anything go wrong.

    Clipboard01.jpg

    Clipboard02.jpg

    Ok, I understand now. But it seems like the themes have to be made for the latest version of Windows, don't they? I'd like a Windows 7 like theme, but I am reluctant to try something from 2016 (the only one I found).

  7. But I can create a theme and use it without problems - I mean otherwise there wouldn't be the "use custom theme" option etc., where I can apply what I previously customized.

    How do you define third party theme anyway? And is this new to Windows 10? I tried googling around and found pretty much nothing.

×
×
  • Create New...