All Activity

I don't know if this has already been mentioned here. Installing and removing extensions works perfectly in Thorium. Unfortunately, updating extensions does not. In my installation of Thorium SSE2 122.0.6261.168 WINXP x32, it does not matter whether the update is done by dragging and dropping the CRX file or by unpacking the extension (in developer mode). Both methods do not work as expected in a standard installation of Thorium, at least for me. Therefore, I changed some settings and installed the Chromium Web Store extension. Now, I can update my extensions simply by dragging and dropping the CRX file. And what I was always missing in Thorium, the Chromium Web Store badge additionally shows a red number indicating that updates are available. A click on the badge and then on the name of the offered extension update leads to the download of the latest version, which of course has still to be installed manually, based on my changed settings in Thorium. BTW, that's a very convenient method to directly archive all extension updates as I always do.

trying to port NSS 3.42 Beta to VC2005, it builds but seems not working.

wrest

Wayback Alienware?

crest

crust

crush

Brush

Anything can be, but the document specifically says POLICY not Command Line Switches: https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline?hl=en Also with Command Line Switches the browser will not have typing: "managed by the organization". I assume that this will be the criterion for application to enterprises.

Brash

You're welcome! Did you check the result manually? Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger] "Status"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Audio] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Circular Kernel Context Logger] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\DiagLog] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Microsoft-Windows-Backup] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Security] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\NBSMBLOGGER] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\NtfsLog] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\PEAuthLog] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\RAC_PS] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\RdrLog] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\SQMLogger] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\TCPIPLOGGER] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WdiContextLog] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WFP-IPsec Trace] "Start"=dword:00000000

It's safe to emulate a processor instruction set, it's just a programme, but emulation is much slower than native execution so you probably won't like the performance.

Processor instructions emulator https://www.intel.com/content/www/us/en/developer/articles/tool/software-development-emulator.html

Much more simpler solution is to add it in the form of a flag. --enable-features=ExtensionManifestV2Availability No quotes, commas, exclamation marks, mysterious signs or ancient runes needed.

trash

crash

grash https://www.definitions.net/definition/grash

Probably like me, other users will have sent a report.

You could add dummy ports in Win.INI then the next port to install will be named the next in the list. Remove redundant ports in Win.INI. Example of port config under [Ports] is COM2:=9600,n,8,1,x

I read some MSFN members fearing Chrome 127 for MV3. There is no reason. MV3 adblockers already exist. It is also possible to implement the "ExtensionManifestV2Availability" policy that will support MV2 extensions for 1 more year. This, of course, does not mean that some of these extensions would experience slowed or no development compared to MV3 extensions from their developers. I also read that some developers aim to support MV2 extensions like Firefox. The Mozilla team will support MV2 extensions for at least 1 year. Basically what you can do in Chromium-based browsers with the policy written above. Then they will reserve their decision. In my opinion there is no purpose to support MV2 extensions longer (whether their development will be abandoned by their own developers).

Let's just wait until we see the first author tool that removes or stips ads from Windows 11. Then we'll see how Microsoft reacts to the Community... Dozens of new AI tools to help them rewrite Windows from scratch and make it a lot better, yet they're wasting resources to make it even worse.

Locked at OP's request.

KB2819745 is Powershell 4.0, you don't need to install it You can update directly to PS 5.1 (Win7AndW2K8R2-KB3191566-x64.zip) here : https://www.microsoft.com/en-us/download/details.aspx?id=54616 On Windows 7 the only requirements are NET 4.5 (or higher) and SP1

Grasp

I installed it normály and it works, have not tried anything related to portable.