Leaderboard

Plenty of other people thought exactly the same! https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-2004-optimizationdefrag-bug/4c5498b9-04fe-41c9-8535-ed10313b6f33 This is off-topic of course, in this forum section, letalone this thread, but what was really bad is that they apparently acknowledged and fixed the issue in an insider build, but then still let the fault get through to the release version of Windows 10 2004! What was really bad was not so much that the automatic optimisation of drives was not having its status remembered so it was running unnecessarily, but it was that it was also misidentifying drive types, resulting in it trying to TRIM conventional hard drives (impossible) and actually defragmenting SSD drives, which is definitely a no-no! It's fixed now anyway, but I do wonder how many people had the lives of their SSD drives unnecessarily shortened by this.

That's really terrible and they should receive a class action for damages for destroying peoples storage. Most SSDs should have a TBW (Terabytes Written) or similar guaranteed/expected lifespan statistic and usually can be viewed via any free SMART interrogator such as crystal diskinfo, victoria, etc, although some of the OEM drives don't always show all the stats. These can give some indication if the drive is getting worn prematurely, or experiencing high temps and can give the user a chance to backup before failure. Of course unexplained catastrophic controller or chip failure is just bad luck. We have all been there at times and it truly sucks having to piece everything back together from backups here and there or recreate it, and some things may be lost forever. Reads should not affect lifetime significantly, but every write counts with SSDs. So think about swapfile, logs, firefoxes' running state saves (timing can be altered in about:config), etc etc. An errant program can write massive amounts to the SSD and the user may be unaware. Use task manager with i/o read bytes and write bytes columns enabled to keep a check just in case. If high throughput, large/frequent dynamic temporary storage is unavoidable, consider the samsung SM range or Intel's business range with very high PTB write endurances.

WinNTSetup - a simple but powerful universal Windows Installer Features: Install (unattend) Windows 2k/XP/20??/Vista/7/8.x/10/11 x86/x64/arm64 Practically runs even on the most minimalistic WinPE selectable drive letter for the new Windows installation Fully automated with save/load setting in ini file and various command line options Install Windows also if nlite/vlite has remove winnt32.exe/setup.exe Integrate Drivers: normal PNP and Textmode Drivers Patch uxtheme to allow unsigned Themes Some common registry tweaks and *.reg file import DISM APPX removal, feature enable/disable Simple VHD creation and Installation Support "Windows to Go" for Windows 7 and later installs Supports WimBoot and CompactOS option for Windows 7 and later Supports all current WIM files: WIM/SWM/ESD and ISO files WinCapture - capture a Windows installation to WIM or ESD file MinWin - simple trimming WIM in memory before apply WinCopy - copy an existing Windows installation to another partition Offline Hotfix uninstall Offline password reset Not Supported: - No Windows embedded version (this includes WinFLP) - No upgrades of existing installations About driver installation: Every driver added in NT6.x windows will be added to the driver store. So it's not recommended to add countless driver, but rather more really required ones. NT5.x massstorage driver integration is possible thanks to Mr dUSHA powerful MSSTMake.exe tool To the Unattend option: It's possible to use an unattend.xml to run the Setup unattended. But as the actual WinPE Setup Phase isn't effective in that way of install, all Winpe related settings inside the unattend.xml won't be applied. Ini config file It's possible to save all GUI-settings to a ini file: push Ctrl + S to save all settings to an ini. push Ctrl + L to load all settings from an ini. A WinNTSetup.ini file in the same dir as the app itself will be loaded automatically at startup. It also can be selected via command line: WinNTSetup.exe /cfg:"C:\mysettings.ini" If you want to modify ini settings yourself, click-click has made a nice PDF for it. For advanced users there are also hidden settings described in the included WinNTSetup.ini.txt Command line: - Press F1 to get list of all options To install Windows in a VHD file: - requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source - create a partitioned VHD and assign a drive letter (push Ctrl + Shift + V to use build in diskpart wrapper for this) - select the VHD drive as installation drive (make sure you boot drive ist a active primary partition on a physical disk) If you get an Antivirus warning from your AV software, please report it to them as a false positive and let them check it. Current Version: 5.4.1 Download: Mega - MediaFire

... and, then, some!

i got switched to new today without option of going back, fbp and revert wouldnt work fb would not load, so i changed the UA to Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/10.1.2 Safari/605.3.8 it seems atm all is ok again and videos with primetime is ok

Figured it might come to that, I noticed the comment about unauthorized distribution in one of the files shortly after I uploaded it. It doesn't look like much more than an user agent spoofer for facebook.com. Let's see what happens when they go YouTube route...

The author would have to pack the extension separately for old Chrome versions and distribute that version outside of Chrome Store because CRX_VERSION_NUMBER_INVALID. Edit: file removed

Yes, I'm seeing the same thing on my installation of Google Chrome 49. I'll message the author and see what he says. It appears as if the necessary file is missing, but it could still be a compatibility issue I suppose.

Hi I also know a few people who were on Windows 10 and had the same problem ... Windows 10 destroys the ssd very quickly in use. Microsoft is giving a fix for this problem. https://www.extremetech.com/computing/314335-fix-for-potential-ssd-damaging-bug-coming-in-windows-update https://www.techradar.com/news/windows-10-update-fixes-annoying-ssd-drive-issue. i prefer my old xp.

... Now you hush, "young" gentleman! Those people are already extremely p***ed that you, single-handedly, created the Vista Extended Kernel project, so much so that they fear their "support channels" will get overwhelmed by Vista users running their official builds: https://forum.palemoon.org/viewtopic.php?p=198116#p198116 As the saying goes, "No good deed goes unpunished" ...

The site has ceased to open in Russia, with different providers in different cities. Connected through a foreign VPN, and found this topic. Is it really impossible to disable these blocks? At this rate, the whole world will soon be banned, and no one will be able to enter here.