Winapp2.ini
-
Posts
6,470 -
Joined
-
Last visited
Posts posted by Winapp2.ini
-
-
I think the same is true of the ExcludeKey's paired RegKeys
-
https://github.com/MoscaDotTo/Winapp2/issues/383
Is it safe to remove
%LocalAppData%\Chromium\User Data\Default\Web Applications\?
For me this folder only has icons of some extensions (e.g. uBlock Origin, Dark Reader). And they are not removed when you remove corresponding extension. -
https://blog.nightly.mozilla.org/2019/05/22/these-weeks-in-firefox-issue-59/
These Weeks in Firefox: Issue 59
lina May 22, 2019No responses yet
HighlightsWow, what a weekend! Hopefully your add-ons are all working now.
A small set of users are still reporting add-on outages. We suspect that the Master Password and Anti-virus software are interfering with the original fix for those users. We’ve released 66.0.5 to try to handle those cases.
Outreachy interns for this summer have been announced
Mozilla is mentoring 8 students in this round. Thank you to all the mentors and all the applicants!
The Google Summer of Code students and projects have been publicly announced! Check out what folks will be working on this summer!
MattN wrote a blog post summarizing the Password Manager Improvements in Firefox 67Friends of the Firefox team
Here’s a list of all resolved bugs.
Fixed more than one bugChris Frey [:nautilus]
Florens Verschelde :fvsch
Kestrel
lloan:[lloanalas]
Mohd Umar Alam [:umaralam48]
Neha
Tim Nguyen :ntimNew contributors (🌟 = first patch)
Chujun Lu fixed a bug where pressing the Enter key when putting a conditional breakpoint into the Debugger would incorrectly cause a linebreak
🌟 DILIP fixed a spelling mistake in one of our console warning messages
Chris Frey [:nautilus] converted the toolbar context menu strings to Fluent, and also fixed two other Fluent-related bugs
jaril fixed a glitch where sometimes the Debugger would break on an exception unexpectedly
Mariana Meireles got rid of some dead code in AboutRedirector
🌟 Ananth fixed up a styling glitch in the Web Console for console.assert strings
🌟 Myeongjun Go made it so that a better error message is emitted when WebExtensions attempt to insert a bookmark folder into the root folder
🌟 Thomas made it so that we truncate very long strings in the DevTools Inspector info bar rather than let them overflow past the end of the screen
🌟 Mohd Umar Alam [:umaralam48] made it so that the Synced Tabs toggle shows an option to “Hide” in the Synced Tabs list when the sidebar is open, and fixed a glitch where the History Sidebar toggle label was missingProject Updates
Activity StreamA new Contextual Feature Recommendation for Sync is coming to the bookmark Star UI
"Sync your bookmarks everywhere" recommendation in the star UI
A lot of improvements and fixes to the new Pocket New Tab, specifically around network failure states.
Add-ons / Web Extensions
Rob Wu added browser console warnings in 68 for proxy APIs that will be deprecated in 71.
Mark Striemer has finished nearly everything remaining for HTML about:addons MVP for 68.
Shane Caraveo added cookieStoreId to webRequest APIs and exposed the private browsing flag in proxy/webRequest details.
Luca Greco added the ability to submit an abuse report on an installed extension from about:addons.
Kris Maglione fixed the theme header background image caching issue for converted LWTs (since they’re all static themes now).
…and everyone is reviewing like crazy to get things in 68 as planned because this weekend was “relaxing downtime” before soft code freeze.Applications
LockwiseRebranding going on this week.
The team is working on polishing the extension for an initial release, and then integrating the extension into desktop Firefox.Firefox Accounts
Ed and Vlad are finalizing the sign-in UX for Fenix, our next-generation Android browser 🚦
Ed landed Rust APIs for FxA device registration and New Send Tab. Grisha is working on integrating this into Android Components so that Fenix can use it 📑Sync and Storage
Mark has an RFC for a sync manager in Rust, to orchestrate syncing of multiple data types 🔄
Thom landed code to import Firefox for iOS bookmarks into the Rust bookmarks component. The next iOS release will use the bookmarks component, and offer bookmark editing! 🔖
Ed is continuing to migrate our crypto backend to NSS 🔒
Lina has been working on adding telemetry for Android and iOS 🔍, and enabled the new bookmark sync by default in Nightly and Beta 📚Push
Jonathan and JR are bringing Push for internal Mozilla consumers (New Send Tab, FxA verification) to Fenix! 📣
Browser Architecture
RKV conversions have been rolled back for now while we investigate issues migrating from 32-bit to 64-bit builds.
browser.html conversion ready to go, but waiting until the next cycle.
Fluent cache for chrome documents ready to land. This will fix corner cases where DOM mutations might not trigger Fluent updates.Developer Tools
ConsoleJefry Lagrange added a way to export console output to a file in bug 1517728.
“Copy as Fetch” and “Use in console” have been added to the network monitor context menu in bug 1540054.
When CSS warnings are displayed in the console, you can now expand them (like a console group) to reveal all the DOM nodes that this warning applies to. So it allows you to jump from a CSS warning in the console directly to the inspector.Screenshot of expanded CSS warning showing affected elements
DebuggerWork on DOM & Event breakpoints started
Progress with captured stacks for various errors appearing in the Console panel (for web developers) or Browser Console window (for browser + addon developers).Network
Local HTTP requests are marked as secure now (bug).
Screenshot of `localhost` with green lock icon in Network monitor
Remote DebuggingDevTools shortcuts now supported in about:devtools-toolbox (bug)
Favicons and user friendly titles for about:debugging and about:devtools-toolbox (bug)Screenshot of wrench and window favicons for debugging and toolbox
Closable error messages (and UI cleanup) (bug)
Screenshot of "connection failed" error and "connection still pending" warning with close buttons
DocumentationNew MDN page for Logpoints
Set a breakpoint page updated to show column breakpointsFission
Subframe crashing UI landed
Here’s a video demonstration
Enn is working on getting BrowserTabChild ported to Fission
mconley is going to work on getting PermitUnload working properly with out-of-process iframesLint
l1nt, which checks for common mistakes in en-US files, and warns on ID conflicts between central/beta/release, is now enabled.
Example on phabricator: https://phabricator.services.mozilla.com/D29001
autoland: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&group_state=expanded&revision=2f1af0a1f129d6af5073c1b53fd15bc5bacb50b0&selectedJob=245063123Mobile
Android ComponentsSupport for built-in WebExtensions has been added! The new Reader View feature component (in Fenix and Reference Browser) is built on top of this.
Password Manager
Work continues on the breakdown of integrating the new management UI, a base patch for the desktop implementation is ready to land.
Minimal scope for password generation via autocomplete was defined and most bugs have been filed.
Data on adoption of autocomplete=“new-password” was gathered as part of the password generation investigation.Performance
New startup main-thread IO test will be enabled on non-debug Desktop builds soon!
Patch to not load userContent.css in the parent process landed and bounced. After some discussion, we’ve decided to put loading userChrome.css and userContent.css behind a default-off pref
This should allow us to avoid searching the disk for those files on start-up for users that don’t have those customizations, which will improve start-up performance.
aswan did some detective work and found some nice places where we can improve start-up time in the AddonManager for brand new profiles
dthayer is investigating compressing various things with lz4 rather than deflate
Gijs has a patch underway to avoid reading chrome.manifest files when not necessary
Gijs made file renaming / moving cheaper on Windows in the common casePerformance tools
Welcoming Raj Meghpara, our new GSoC student! He’s going to work on Instruments import support for Firefox Profiler.
Network tooltips are now displayed as soon as the line is hovered.
The publishing flow has been streamlined (ux issue)New look of publish panel in Firefox Profiler with inverted checkboxes
More tools in the web console:
List of available profiler information in the console
MOZ_PROFILER_HELP env variable gives help to profile Firefox startup.
Picture-in-Picture
Holding to Nightly while we iterate.
Please keep filing bugs against this meta bug if you notice anything strange. Thanks!
Fixed
Clicking on the Picture-in-Picture toggle no longer sends mouse events to content
The toggle no longer appears when in fullscreen
The controls (mostly) disappear after 3 seconds on the player window when not hovering
Fixed strange borders showing up when switching focus between the player window and other windows
Made the player window easier to resize
Soon to be fixed
Player buttons look strange on “tall” videos
RTL support
Keyboard accessibility
And loads of polish!Privacy/Security
To combat malicious malware sites, Paul made us disallow add-on installation prompts in full-screen.
Because it went so well, we are going to extend our experiment for requiring user interaction for Notification permission prompts to Beta.
Another blog post coming soon
We also landed the telemetry pieces to do the announced release measurements on permission prompt usage in 67 release. This will hopefully allow us to narrow down on a set of good heuristics for automatically blocking.
Prathikshalanded the first piece of her internship project to simplify and robust-ify the way about:certerror communicates with the parent process.
Jonas continues to remove all the eval() usage in our chrome-privileged code.
Small improvements to DNS over HTTPS UI in settings/preferences let you pick from resolversSearch and Navigation
SearchLooking into consequences and prevention after the add-ons certificate problem: Search Service initialization should be more robust
New Baidu search code deployed as system add-onQuantum Bar
Fixed 19 Bugs in the last 2 weeks
Quantum Bar is enabled by default in Firefox 68 🎉🎉🎉
Still working on a few remaining bugs
Designing and discussing WebExtension APIs for the first experimentBleeding edge browsing
Download Firefox Nightly
-
https://hacks.mozilla.org/2019/05/firefox-67-dark-mode-css-webrender/
Firefox 67: Dark Mode CSS, WebRender, and more
By Dan Callahan
Posted on May 21, 2019 in Featured Article, Firefox, and Firefox ReleasesFirefox 67 is available today, bringing a faster and better JavaScript debugger, support for CSS
prefers-color-schememedia queries, and the initial debut of WebRender in stable Firefox.These are just the highlights. For complete information, see:
CSS Color Scheme Queries
New in Firefox 67, the
prefers-color-schememedia feature allows sites to adapt their styles to match a user’s preference for dark or light color schemes, a choice that’s begun to appear in operating systems like Windows, macOS and Android. As an example of what this looks like in the real world, Bugzilla usesprefers-color-schemeto trigger a brand new dark theme if the user has set that preference.
The
prefers-color-schememedia feature is currently supported in Firefox and Safari, with support in Chrome expected later this year.Additionally, the
revertkeyword is now supported, making it possible to revert one or more CSS property values back to their original values specified by the user agent’s default styles (or by a custom user stylesheet if one is set). Defined in Cascading and Inheritance Level 4,revertis also supported by Safari.WebRender’s Stable Debut
Nearly four years ago we started work on a new rendering architecture for Firefox with the goal of better utilizing modern graphics hardware. Today, we’re beginning to gradually enable WebRender for users on Windows 10 with qualified hardware. This marks the first time that WebRender has been enabled outside of Nightly and Beta builds of Firefox, and we hope to expand the supported platforms in future releases.
You can read more about WebRender in The whole web at maximum FPS: How WebRender gets rid of jank.
More Capable DevTools
Firefox 67 and 68 Developer Edition bring enormous improvements to Firefox’s JavaScript Debugger. Discover faster load times, amazing support for source maps, more predictable breakpoints, brand new logpoints, and much more.
We’ve collected the Debugger improvements in their own article: Faster, Smarter JavaScript Debugging in Firefox DevTools.
In addition to the Debugger, the Web Console saw numerous updates, including greater keyboard accessibility and support for importing modules into the current page.
We’ve also removed or deprecated a few seldom-used and experimental tools, including the Canvas Debugger, Shader Editor, Web Audio Inspector, and WebIDE.
Browser Features
Side-by-Side Profiles
Firefox now defaults to using different profiles for each installed version, making it easier than ever to run multiple copies of Firefox side-by-side.
In addition, the browser will warn you if you try to open a newer profile with an older version of Firefox, as such mismatches can occasionally lead to data loss. This protection can be bypassed with the new
-allow-downgradecommand line argument.Enhanced Privacy Controls
Firefox 67 better protects your privacy online with new Content Blocking options to avoid known cryptominers and fingerprinters.
You also have more control over your extensions, which can be prevented from running in private browsing windows.
This is the default for all newly installed extensions in Firefox 67, though your previously installed extensions will receive permission by default. You can adjust these permissions on a per-extension basis by visiting about:addons.Easier Access to Firefox Accounts and Saved Passwords
We’re working hard to make Firefox Accounts more useful and discoverable this year, starting with a new default icon in the browser toolbar.
The new icon indicates whether or not you’re signed into a Firefox Account, and makes it easy to perform actions like sending tabs to other devices or manually triggering a sync. Like other toolbar buttons, you can freely move or hide the Firefox Account button according to your preferences.
Check out the many improvements to Firefox’s built-in password manager, including quicker access to your list of saved credentials. You can either click on the new “Logins and Passwords” item in the main menu, or the new “View Saved Logins” button in the login autocomplete popup.
This can be especially useful if you need to look up or edit a login outside of the normal autofill workflow. And, if you use Firefox Sync, you can access your saved passwords with the Firefox Lockbox app for Android or iOS.
Web Platform Features
Support for legacy FIDO U2F APIs
We’ve enabled legacy FIDO U2F support to improve backwards compatibility with sites that have not yet upgraded to its standards-based successor, WebAuthn.
These APIs make it possible for websites to authenticate users with strong, hardware-backed authentication mechanisms like USB security keys or Windows Hello.
AV1 on Windows, Linux, and macOS
Firefox now supports AV1, a next-generation video codec, on all major desktop platforms. Also, playback on those platforms is now powered by dav1d, a faster and more efficient AV1 decoder developed by the VideoLAN and FFmpeg communities.
JavaScript:
String.prototype.matchAll()and Dynamic ImportsFirefox joins Chrome in supporting the
matchAll()String prototype method, which takes a regular expression and returns an iterator of all matching text, including capturing groups.The
import()function can now be used to dynamically load JavaScript modules, similarly to how the static import statement works. Now it’s possible to load modules conditionally or in response to user actions, though such imports are harder to reason about for build tools that use static analysis for optimizations like tree shaking.And more awaits!
This release includes plenty of other fixes and enhancements not covered here, and lots more to come. So what are you waiting for? Download Firefox 67 today and let us know what you think!
-
It's functional but lacking support for things you'd expect from mainline firefox (ie. webextensions support - planned but not implemented in GeckoView). I haven't experienced any issues but i use Focus as my default browser and only spin up Fennec or Fenix sparingly
It's definitely worth checking out if you're interested, it does not conflict with any existing Firefox installations on your phone
-
Fenix is now available on the Play Store through the beta/nightly process.
https://events.mozilla.org/becomeabetatestingbughunter
This is the upcoming rewrite of Firefox for Android (fennec) to be based on GeckoView (a la Firefox Focus and Reference Browser). It's been available via task cluster for a while but being on the playstore means automated installs etc
-
1 hour ago, CSGalloway said:
I think it would be a good suggestion if a similar readme post could be added near the front of this thread..... here...
OE Classic is a replacement for Outlook Express.....
I added a link directly to the Creating Entries section of the ReadMe to the top level post. For sanity/version control reasons, it's much easier to link to GitHub resources from this thread than to maintain separate copies
-
On 5/5/2019 at 01:53, ricktendo64 said:
Any chance you could add Outlook Recent Searches https://www.howto-outlook.com/howto/clearmru.htm
[Outlook Recent Searches *] LangSecRef=3021 Detect1=HKCU\Software\Microsoft\Office\11.0\Outlook Detect2=HKCU\Software\Microsoft\Office\12.0\Outlook Detect3=HKCU\Software\Microsoft\Office\14.0\Outlook Detect4=HKCU\Software\Microsoft\Office\15.0\Outlook Detect5=HKCU\Software\Microsoft\Office\16.0\Outlook Default=True RegKey1=HKCU\Software\Microsoft\Office\11.0\Outlook\Profiles\Outlook\0a0d020000000000c000000000000046|101f0445 RegKey2=HKCU\Software\Microsoft\Office\12.0\Outlook\Profiles\Outlook\0a0d020000000000c000000000000046|101f0445 RegKey3=HKCU\Software\Microsoft\Office\14.0\Outlook\Profiles\Outlook\0a0d020000000000c000000000000046|101f0445 RegKey4=HKCU\Software\Microsoft\Office\15.0\Outlook\Profiles\Outlook\0a0d020000000000c000000000000046|101f0445 RegKey5=HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\Outlook\0a0d020000000000c000000000000046|101f0445
I post the default profile name Outlook but this may vary, is there a way for winapp2ool to query the registry for the profile name and replace "Outlook"?
Would all subkeys of \Profiles\Outlook\***** necessarily be a profile folder? If so this wouldn't be too difficult to create support for, I don't think.
-
My nightly seems unaffected by this bug. I have the message saying the addons can't be verified but they all still work. Weird. Addon signing is probably not a requirement on the nightly build if I had to guess
edit: seems my xpinstall.signatures.required is set to False
-
4 minutes ago, Andavari said:
Only if cleaned improperly. Referring to reoccurring folders like CryptnetUrlCache in most cleaners, etc.
Oh I know! In the immediate future, I'm looking towards implementing unit tests, but winapp2ool has some in-progress ideas for metascripting entries, a windows store application one would fit in well
-
On 2/21/2019 at 06:49, Andavari said:
Too bad CCleaner (or some other tool) doesn't exist to completely simplify and hasten the ability to make new cleaning entries/routines for the lot of repeating sub-folder structures without having to make unique individual cleaners which seems to be a reoccurring theme for Win10.
I hear minefields can be dangerous
-
A build of winapp2ool with the non-ccleaner ini being a commandline arg (-ncc) is now available. The menus in diff or trim might be broken under some circumstances, but I think I got most of the adjustments correct.
https://github.com/MoscaDotTo/Winapp2/tree/Branch1/winapp2ool/bin/Debug
-
38 minutes ago, SMalik said:
[Notepad++ Backups *] entry should be removed.
Agreed, I think it should be moved to winapp3.ini specifically
The backups folder becomes polluted with backup files that notepad++ has "forgotten" over time, mine has over 40 0kb backups of files that I never created. Normally I'd say we should just remove it because most users wouldn't want to delete these, but given this issue I think there's a case for the usefulness of the entry
-
3 hours ago, siliconman01 said:
No, I did not. Disabling it did do the trick. Can we set the default on 2 back to Disabled. This extra step to perform a TRIM is not at all self intuitive.
This change was made across all modules under the assumption that most people would usually want to download the latest. The default download setting now matches whether or not you have an internet connection.
I actually just had the realization that this has likely had the affect of also inverting any commandline args for downloading (outside the download module) as I typed this response, so I've reverted the change on the development branch. You can find an executable with the behavior you want here: https://github.com/MoscaDotTo/Winapp2/blob/Branch1/winapp2ool/bin/Debug/winapp2ool.exe
I'd also like some feedback on whether or not the non-ccleaner setting should be shown or if it should be behind a commandline arg (eg winapp2ool -ncc) which would set winapp2ool to non-ccleaner mode. The user facing change here would be that all the separate menu options for the non-ccleaner version would no longer be shown and the winapp2.ini options would select the appropriate file for your current mode. If for some reason someone wanted to still use the combined mode, I could leave support in for that through some other arg, but I would imagine there are not many people frequently interacting with both copies at the same time.
In the near future I'm hoping to extend the commandline arg handling to better enable people to use winapp2ool however they want in a scripted fashion, which should hopefully eliminate the need for potentially confusing menu setups like this.
-
-
Mozilla could end up down this route too:
https://blog.mozilla.org/addons/2018/10/26/firefox-chrome-and-the-future-of-trustworthy-extensions/
Manifest v3
“In 2019 we will introduce the next extensions manifest version…We intend to make the transition to manifest v3 as smooth as possible and we’re thinking carefully about the rollout plan.”
In 2015, Mozilla announced we were deprecating our extremely popular extension system in favor of WebExtensions, an API compatible with Chrome, as well as Edge and Opera. There were several reasons for this, but a large part of the motivation was standards — a fundamental belief that adopting the API of the market leader, in effect creating a de facto standard, was in the best interests of all users.
It was a controversial decision, but it was right for the web and it represents who Mozilla is and our core mission. Three years later, while there still isn’t an official standard for browser extensions, the web is a place where developers can quickly and easily create cross-browser extensions that run nearly unchanged on every major platform.
So I would like to publicly invite Google to collaborate with Mozilla and other browser vendors on manifest v3. It is an incredible opportunity to show that Chrome embodies Google’s philosophy to “focus on the user,” would reaffirm the Chrome team’s commitment to open standards and an interoperable web, and be a powerful statement that working together on the future of browser extensions is in the best interests of a healthy internet.
-
https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23
Comment 23 by rh...@raymondhill.net, Yesterday (32 hours ago)In the design document, it is said that the webRequest API will no longer allow to be used in blocking mode:
> In Manifest V3, we will strive to limit the blocking version
> of webRequest, potentially removing blocking options from most
> events (making them observational only). Content blockers should
> instead use declarativeNetRequest (see below). It is unlikely
> this will account for 100% of use cases (e.g., onAuthRequired),
> so we will likely need to retain webRequest functionality in
> some form.From the description of the declarativeNetRequest API[1], I understand that its purpose is to merely enforce Adblock Plus ("ABP")-compatible filtering capabilities[2]. It shares the same basic filtering syntax: double-pipe to anchor to hostname, single pipe to anchor to start or end of URL, caret as a special placeholder, and so on. The described matching algorithm is exactly that of a ABP-like filtering engine.
If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin ("uBO") and uMatrix, can no longer exist.
Beside causing uBO and uMatrix to no longer be able to exist, it's really concerning that the proposed declarativeNetRequest API will make it impossible to come up with new and novel filtering engine designs, as the declarativeNetRequest API is no more than the implementation of one specific filtering engine, and a rather limited one (the 30,000 limit is not sufficient to enforce the famous EasyList alone).
Key portions of uBlock Origin[3] and all of uMatrix[4] use a different matching algorithm than that of the declarativeNetRequest API. Block/allow rules are enforced according to their *specificity*, whereas block/allow rules can override each others with no limit. This cannot be translated into a declarativeNetRequest API (assuming a 30,000 entries limit would not be a crippling limitation in itself).
There are other features (which I understand are appreciated by many users) which can't be implemented with the declarativeNetRequest API, for examples, the blocking of media element which are larger than a set size, the disabling of JavaScript execution through the injection of CSP directives, the removal of outgoing Cookie headers, etc. -- and all of these can be set to override a less specific setting, i.e. one could choose to globally block large media elements, but allow them on a few specific sites, and so on still be able to override these rules with ever more specific rules.
Extensions act on behalf of users, they add capabilities to a *user agent*, and deprecating the blocking ability of the webRequest API will essentially decrease the level of user agency in Chromium, to the benefit of web sites which obviously would be happy to have the last word in what resources their pages can fetch/execute/render.
With such a limited declarativeNetRequest API and the deprecation of blocking ability of the webRequest API, I am skeptical "user agent" will still be a proper category to classify Chromium.
---
[1] https://developer.chrome.com/extensions/declarativeNetRequest
[2] https://adblockplus.org/filter-cheatsheet
[3] https://github.com/gorhill/uBlock
[4] https://github.com/gorhill/uMatrix
QuoteWith such a limited declarativeNetRequest API and the deprecation of blocking ability of the webRequest API, I am skeptical "user agent" will still be a proper category to classify Chromium.
-
25 minutes ago, APMichael said:
I think you mean that we should merge all the individual entries into one [Xbox *] entry, right?
Do you think we can use the following FileKey for this? Otherwise the entry will be very large.
FileKeyX =%LocalAppData%\Packages\Microsoft.Xbox*_*\
This would affect the "Microsoft.XboxOneSmartGlass_8wekyb3d8bbwe" package, is it part of the Xbox app too?
-
1 hour ago, siliconman01 said:
Thanks very much for all your work and expertise on this extremely useful tool. Happy holidays!
Happy holidays!
-
the tools folder and its now-deprecated contents are also removed from the repo, with the exception of the winappool executable and its version file for watershedding.
-
winapp2ool is released! 1.0
https://github.com/MoscaDotTo/Winapp2/releases/tag/v1.0
Users of the beta should be able to update from their old builds to a watershed beta build (0.99) which should then prompt them to update to 1.0 (this is necessary because the files have moved around on the repo with this release). Alternatively, you can simply download the 1.0 build from the release page here.
Thank you for all your feedback over the last year on winappdebug, ccinidebug, and winapp2ool as a whole
-
I've made available a draft of a readme for winapp2ool.exe that should apply to the upcoming 1.0 release. It is not entirely accurate for 0.85 which is the current master version on the GitHub
-
Off to the removed entries.ini with them!
-
8 hours ago, nukecad said:
AKA advertising pop-ups.
At least they can currently be turned off in 'Options', but is this the first foot on the slippery slope?
I understood this to mean to the new doorhangers calling attention to features like content blocking, I use nightly and haven't seen any advertisements (yet..?)
Winapp2.ini additions
in CCleaner
Posted
Would those filekeys be okay in [Windows Logs *]?