UCyborg

Member
  • Content count

    222
  • Joined

  • Last visited

  • Days Won

    1

UCyborg last won the day on March 31

UCyborg had the most liked content!

Community Reputation

61 Excellent

1 Follower

About UCyborg

  • Birthday

Profile Information

  • OS
    Windows 8.1 x64
  • Country

Recent Profile Visitors

1,073 profile views
  1. True, insufficient for shortcut, but enough if using Run dialog. You're specifying 2 GUIDs in your shortcuts, it seems the second one is sufficient. If you replace themecpl.dll and themecpl.dll.mui with the ones from Windows 8.1, links open classic dialogs, but the Display link remains unfucntional, it just opens Libraries. You could probably set up those DLLs to live in peace with new ones with a trick I described in Restoring Manage Wireless Networks GUI on Windows 8+. Managed to bring back Display shortcut to the Control Panel itself, it just puzzles me why Personalization doesn't appear even though it's registered, everything is correct according to this. Maybe MS blacklisted that GUID. Win10 is mess either way. Here's another shell command: shell:::{ED834ED6-4B5A-4BFE-8F11-A626DCB6A921}\pageWallpaper
  2. Updated another laptop to CU. After a bit lengthy update process, things seemed fine at first glance, a bit slower at first; for some reason, OneDrive process was eating disk and CPU despite policy being in place that should prevent it from running, fortunately, it hasn't spawned since (one-time setup thing?). Settings for which security related things warnings should show up weren't preserved, and I had to flip a switch for preventing UWP apps from running in the background. If I remember correctly, AU didn't have it, just the switches for individual apps. Now here comes the strangest thing, that either carried over the upgrade process or was introduced by it. The damned thing for some reason refuses to let user move any icon on the desktop to the bottom-left corner, anything placed there gets moved 2 places to the right. Haven't dealt with icon layout problems in a long time, looks like they can still occur. I cleared Bags and BagMRU keys in registry, but the problem persists. What's funny, I once managed to get one of the icons to stick there for a while with the help of Sort by command, it even survived exiting the shell by holding SHIFT + CTRL, right-clicking the taskbar and selecting Exit Explorer. It didn't survive exiting Explorer for the second time.
  3. Looks like those settings aren't completely gone yet (at least in current stable build 15063.483), they deleted references to them from registry. Importing DisplayCPL.reg brings them back. TrustedInstaller privileges required. They did replace the scaling slider with the link to the Settings app. TrueType tuner is there, font sizes can be changed, color calibrator works at first glance, also the link "Adjust brightness" that points to the power panel appears on supported devices eg. laptops. Edit: Also noticed that reference to Personalization settings is present in registry, so I guess it doesn't appear in Control Panel because something about that specific panel is broken, though it can be invoked using Run dialog: shell:::{ED834ED6-4B5A-4BFE-8F11-A626DCB6A921} Should be invokable with this one as well, but it doesn't budge... control.exe /name Microsoft.Personalization
  4. Updated wlanpref2.reg to add a shortcut to the Control Panel under Network and Internet. Can also be invoked with: control.exe /name Microsoft.ManageWirelessNetworks
  5. I'd try those two classic commands first in Command Prompt run as Administrator: Dism /Online /Cleanup-Image /RestoreHealth sfc /scannow Ideally, they would repair everything wrong with system files and certain registry entries and let the offending update to uninstall cleanly afterwards. There is a chance that when update uninstallation fails, that something useful might be written at the end of the log file C:\Windows\Logs\CBS\CBS.log
  6. @NoelC I can confirm it still happens on non-tweaked version 1703.
  7. Indeed nothing to be excited about. Maybe it could work as a basic file manager on a phone. I wonder what finished version of Win10 would be like. Re-inventing the wheel gone really bad. And you never know what they'll throw out next. Currently, they really hate the Control Panel. What's next? Right, have to remember about version numbers. The days of counting service packs are gone.
  8. They have more detailed list of additions here.
  9. One of those things they don't mention in the highlights of the updates, given the emphasis on the UWP landscape, BitLocker got some enhancements with Windows 10, XTS-AES encryption algorithm and according to this, the encryption process is supposedly faster in Creators Update. I wonder if someone knowledgeable tested that claim. Either way, the mindset behind Win10 development isn't the same like it was with Win7, one of the reasons the OS is still odd at places. 3D Paint and new emojis, one of those main highlights of the Creators Update. Gets one to think they're running comedy show at MS. I think highlighting actual core improvements would be a good idea. Maybe with the next feature update? No one would oppose if they fixed things they broke that worked in older versions. Another thing that comes to mind. Will classic Explorer see any changes in the future? There's already UWP File Explorer present in Creators Update: explorer shell:AppsFolder\c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App It needs some work before it would be equivalent functionality wise to the classic Explorer.
  10. I do use PotPlayer for videos and AIMP for audio, just have those codecs installed for Windows' own media framework to be able to support as much formats as possible, in case they're needed by something else, in this case QTTabBar. Its preview feature allows hovering over the file and it will play without having to open it in external player. I assume it relies on whatever .NET Framework provides for media playback, so extra codecs are needed for otherwise unsupported formats. Just in case, I also tried with minimum amount of codecs on fresh Windows 8.1 install in a virtual machine, just took the ones from https://www.xiph.org/downloads/ to add support for OGG and FLAC among others, but QTTabBar outputs the same error code. Repeat the same procedure on Windows 7 or 10 and it works.
  11. There is an odd issue when it comes to Explorer extension QTTabBar's preview feature, specific to Windows 8.1 (maybe 8 as well). If you try to preview a media file, eg. FLAC or OGG, for which you need to install extra codecs/DirectShow filters, it spits out said error code instead of playing the file. Windows Media Player plays the file just fine. If the codecs aren't installed, you get generic "Failed to load media file.", as expected. On both Windows 7 and 10, installing K-Lite Codec Pack enables playback of such files both in WMP and Explorer itself with the help of QtTabBar. There's something weird about Explorer on Windows 8.1 where the files don't play, expect those that don't require additional codecs. Haven't found anything useful regarding the error code, it's mostly encountered in WMP itself. It seems as if something was missing when it comes to ability to utilize codecs from Explorer's side since formats with native support do play without a hitch. Any idea what the issue is and how to solve it?
  12. Diagnostic Tools do not work with disabled VsHub.exe. PS: I'd like to note that the meaning of "server" depends on the context. It can be used for nothing more than inter-process communication. Though they do acknowledge that telemetry is also part of VS Hub. VS2017's VS Hub hosts more functionality of the IDE, probably why it refuses to work without it. I'd say if you find the whole thing fishy, probably the best to not use the software at all, rather than worrying about what each process hosts. At least that would be good for sanity.
  13. What you're seeing is DWM jumping in and replacing hung app's window with a ghost copy. Ghost copies have standard frame which will have glass effect if Aero Glass is installed. The app would hang irregardless of whether Aero Glass is installed or not. If the app hangs and doesn't process window messages (events) for at least 5 seconds, this happens, otherwise, you wouldn't be able to interact with the window at all, this way, you get to see last visual state in which the app was in before it hung and you can get the window out of the way (move it, minimize it or force close the app). You see the same thing if a modern version of Visual Studio or Office app hangs, which got some people thinking Aero Glass could somehow override the custom frame. Standard frame is there because at that point, the app's code providing custom frame isn't running anymore. You can set opacity to maximum with Aero Glass GUI. The only other way is stopping Aero Glass's task via Task Scheduler then forcibly stopping Desktop Window Manager via Task Manager, which restarts it without Aero Glass loaded. There's no function that would unload Aero Glass at will. As a point of interest for the geeks out there, it is possible to process window messages in a way that makes DWM itself think that the app is not responding, even though it works fine. Old games by Surreal Software have the main loop written somewhat like this (pseudo C code derived from disassembled code): while (1) { MSG msg; BOOL result; if (PeekMessage(&msg, NULL, WM_KEYFIRST, WM_KEYLAST, TRUE) || PeekMessage(&msg, NULL, WM_MOUSEFIRST, WM_MOUSELAST, TRUE)) { if (msg.message == WM_QUIT) break; TranslateMessage(&msg); DispatchMessage(&msg); continue; } result = PeekMessage(&msg, NULL, 0, 0, TRUE); if (msg.message == WM_QUIT) break; if (result == TRUE) DispatchMessage(&msg); Game_Frame(); } If you run the game in windowed mode, then click outside the window to make it lose focus, it appears frozen after 5 seconds, even though it still runs its loop, can even see what's happening in-game in ghost window, it just doesn't respond to user input. Accent color change event can thaw it. Simplifying the loop to have one PeekMessage call without filtering, then TranslateMessage and DispatchMessage if the result from PeekMessage was positive, then finally running the game frame resolves the issue.
  14. It also opens faster that way. By default, when you add explorer.exe, the new process should terminate right away, unless the setting to open folder windows in separate process is enabled in Folder Options. I did notice in the past that after some usage, the explorer.exe process hosting windows doesn't terminate, even long after all windows have been closed. Nope, that would be a good challenge though. netcenter.dll hosts the whole Network and Sharing Center. As with wlanpref.dll, the DLL is smaller on Windows 8+, but Windows 7 version has some extra dependencies. I don't know how to decipher Dependency Walker output to be able to tell what exactly is missing.
  15. Interesting, so the original wlanpref.dll does partially work. It might be possible to just add the Windows 7 DLL, eg. renaming both the DLL and MUI file to wlanpref2, then changing, or preferably, adding new reference in registry with a different GUID (using original GUID and just changing the last number might be enough). The former variant seems to work, have yet to try the latter. There is a catch, TrustedInstaller is the only user that can change that part of registry. I can confirm this is actually possible, no replacing existing files or changing any existing registry entries required. Take the needed files from Windows 7 install and name them wlanpref2.dll and wlanpref2.dll.mui. Open wlanpref2.dll with some hex editor and find the following byte sequence: 86 32 6E ED CD 87 Replace it with: 86 32 6E ED CD 88 Only the last byte differs, the sequence is last part of the GUID. The files can now be copied to appropriate folders on the target system. The last step is putting correct registry entries in place. I'm attaching wlanpref2.reg which can be used to import needed entries. To be able to use it, regedit must be run as TrustedInstaller. To do that, I used Process Hacker with TrustedInstaller Plugin. The GUI can now be invoked with: explorer.exe shell:::{1FA9085F-25A2-489B-85D4-86326EEDCD88}