Windows 10 version 2004 final version still sucks!
-
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug: When you checked the optimization of the systems drive it ALWAYS showed optimization was never done and was required. This resulted in the system continuously running optimization and so reducing the life of SSD drives. Well, today I tried the final release of 2004 and the bug is still there. Every time you restart the machine, it reports optimization was never done. Apparently Microsoft did not bother to fix the bug! Yuck! I restored my last 1909 version from my last 1909 image. MS can keep 2004!
I am not wrong. I am just different!
-
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug: When you checked the optimization of the systems drive it ALWAYS showed optimization was never done and was required. This resulted in the system continuously running optimization and so reducing the life of SSD drives. Well, today I tried the final release of 2004 and the bug is still there. Every time you restart the machine, it reports optimization was never done. Apparently Microsoft did not bother to fix the bug! Yuck! I restored my last 1909 version from my last 1909 image. MS can keep 2004!
I am not wrong. I am just different!
You're aware that you can turn off automatic optimization, right? Administrative Tools->Defragment and Optimize Drives->Change Settings->uncheck "Run on a Schedule"
The difficult we do right away... ...the impossible takes slightly longer.
-
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug: When you checked the optimization of the systems drive it ALWAYS showed optimization was never done and was required. This resulted in the system continuously running optimization and so reducing the life of SSD drives. Well, today I tried the final release of 2004 and the bug is still there. Every time you restart the machine, it reports optimization was never done. Apparently Microsoft did not bother to fix the bug! Yuck! I restored my last 1909 version from my last 1909 image. MS can keep 2004!
I am not wrong. I am just different!
Does Richard's response address your concerns?
Peter Hayward Ngarkat Technologies South Australia,
-
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug: When you checked the optimization of the systems drive it ALWAYS showed optimization was never done and was required. This resulted in the system continuously running optimization and so reducing the life of SSD drives. Well, today I tried the final release of 2004 and the bug is still there. Every time you restart the machine, it reports optimization was never done. Apparently Microsoft did not bother to fix the bug! Yuck! I restored my last 1909 version from my last 1909 image. MS can keep 2004!
I am not wrong. I am just different!
Cp-Coder wrote:
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug:
Only one? :doh: :doh: :mad::mad: X| X| I spent yesterday 3 hours trying to get a Wireless HP Printer working decently... without success. Printing from the HP Own-Software OK. Printing from Word, Text-Pad or whatsoever other app... nothing. Windows Firewall and Antivirus-Firewall temporary disabled... nothing. Trying to get the Settings page from the "print-queue" throws an exception and restarts some background services... (Working perfectly in Win7) Latest drivers and App from HP... no difference at all. I found a report that there was a bug because windows wanted to secure an hacking vector being used through network printers, a KB456... was supposed to be the solution. I download it "Not suitable for this PC", download the other version "not suitable for this PC", download the x86 Version... "Not suitable for this PC" I switched it off, sent it to hell and opened a :beer: Today 2nd round :sigh: :sigh: :sigh: P.S. I tried to get the 1909... nothing (at least not from official sites, and I am not really willing to try any ISO found out there). Do you have any working link for official 1909?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
You're aware that you can turn off automatic optimization, right? Administrative Tools->Defragment and Optimize Drives->Change Settings->uncheck "Run on a Schedule"
The difficult we do right away... ...the impossible takes slightly longer.
-
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug: When you checked the optimization of the systems drive it ALWAYS showed optimization was never done and was required. This resulted in the system continuously running optimization and so reducing the life of SSD drives. Well, today I tried the final release of 2004 and the bug is still there. Every time you restart the machine, it reports optimization was never done. Apparently Microsoft did not bother to fix the bug! Yuck! I restored my last 1909 version from my last 1909 image. MS can keep 2004!
I am not wrong. I am just different!
I'm using Linux, so I don't have a problem with Windows 10 update. :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
You're aware that you can turn off automatic optimization, right? Administrative Tools->Defragment and Optimize Drives->Change Settings->uncheck "Run on a Schedule"
The difficult we do right away... ...the impossible takes slightly longer.
-
Does Richard's response address your concerns?
Peter Hayward Ngarkat Technologies South Australia,
-
Cp-Coder wrote:
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug:
Only one? :doh: :doh: :mad::mad: X| X| I spent yesterday 3 hours trying to get a Wireless HP Printer working decently... without success. Printing from the HP Own-Software OK. Printing from Word, Text-Pad or whatsoever other app... nothing. Windows Firewall and Antivirus-Firewall temporary disabled... nothing. Trying to get the Settings page from the "print-queue" throws an exception and restarts some background services... (Working perfectly in Win7) Latest drivers and App from HP... no difference at all. I found a report that there was a bug because windows wanted to secure an hacking vector being used through network printers, a KB456... was supposed to be the solution. I download it "Not suitable for this PC", download the other version "not suitable for this PC", download the x86 Version... "Not suitable for this PC" I switched it off, sent it to hell and opened a :beer: Today 2nd round :sigh: :sigh: :sigh: P.S. I tried to get the 1909... nothing (at least not from official sites, and I am not really willing to try any ISO found out there). Do you have any working link for official 1909?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Nelek wrote:
I spent yesterday 3 hours trying to get a Wireless HP Printer working decently... without success.
Wireless printers are such a crapshoot. In my experience, it'll either succeed from the get-go, or you'll spend hours trying to get it to work. With no guarantee it'll ever work. Or might work today, but not work again next week. Heck, I have VMs that, for all intents and purposes, are absolutely identical in every way. Some I can reliably print from 100% of the time, and others, configured to print in exactly the same way, to the same printer, will simply claim the printer's offline and refuse to do anything.
-
Cp-Coder wrote:
It was reported weeks ago that the pre-release version of Windows10 version 2004 had a bug:
Only one? :doh: :doh: :mad::mad: X| X| I spent yesterday 3 hours trying to get a Wireless HP Printer working decently... without success. Printing from the HP Own-Software OK. Printing from Word, Text-Pad or whatsoever other app... nothing. Windows Firewall and Antivirus-Firewall temporary disabled... nothing. Trying to get the Settings page from the "print-queue" throws an exception and restarts some background services... (Working perfectly in Win7) Latest drivers and App from HP... no difference at all. I found a report that there was a bug because windows wanted to secure an hacking vector being used through network printers, a KB456... was supposed to be the solution. I download it "Not suitable for this PC", download the other version "not suitable for this PC", download the x86 Version... "Not suitable for this PC" I switched it off, sent it to hell and opened a :beer: Today 2nd round :sigh: :sigh: :sigh: P.S. I tried to get the 1909... nothing (at least not from official sites, and I am not really willing to try any ISO found out there). Do you have any working link for official 1909?
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Quote:
Do you have any working link for official 1909?
No, unfortunately. At the time when you could still get the 1909 install tool, I made a USB installer for 1909. However, I rarely use it. I have Macrium images of 1909 as it was running on my machine. That means it is easy to restore my machine to 1909 as it existed when the image was made.
I am not wrong. I am just different!
-
Quote:
Do you have any working link for official 1909?
No, unfortunately. At the time when you could still get the 1909 install tool, I made a USB installer for 1909. However, I rarely use it. I have Macrium images of 1909 as it was running on my machine. That means it is easy to restore my machine to 1909 as it existed when the image was made.
I am not wrong. I am just different!
Cp-Coder wrote:
I have Macrium images of 1909 as it was running on my machine.
So I am doing it myself for him too... but I have started two days ago... no alternative... 2004. But... at the end I have found 2 possible things that look promising, so tomorrow, restore, try and if working doing a new image just behind it
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Nelek wrote:
I spent yesterday 3 hours trying to get a Wireless HP Printer working decently... without success.
Wireless printers are such a crapshoot. In my experience, it'll either succeed from the get-go, or you'll spend hours trying to get it to work. With no guarantee it'll ever work. Or might work today, but not work again next week. Heck, I have VMs that, for all intents and purposes, are absolutely identical in every way. Some I can reliably print from 100% of the time, and others, configured to print in exactly the same way, to the same printer, will simply claim the printer's offline and refuse to do anything.
I know what you mean... but not my decission. He wants to spare cable...
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
