Profile Informations

Login Datas

or login

First name is required!
Last name is required!
First name is not valid!
Last name is not valid!
This is not an email address!
Email address is required!
This email is already registered!
Password is required!
Enter a valid password!
Please enter 6 or more characters!
Please enter 16 or less characters!
Passwords are not same!
Terms and Conditions are required!
Email or Password is wrong!

Microsoft's Windows 10 1809 Update Officially A Total Train Wreck Of Bugs

Windows 10

I know we're beginning to sound like a broken record, but Microsoft’s Windows 10 October 2018 Update has been beyond disastrous. There have been numerous issues with Microsoft's second major update for Windows 10 this year, with the first one resulting in the October 2018 Update being pulled (and later reinstated in November).

Now we're learning of yet another issue plaguing the Windows 10 October 2018 Update. In this case, it's a cumulative update (KB4467708) that is causing problems with the already troublesome October 2018 Update (also known as Version 1809). The cumulative update was supposed to fix high CPU usage with specific AMD processors following a previous July 2018 update aimed at providing mitigations for Spectre Variant 2.

However, Microsoft is warning that those that use Windows Media Player will be in for a rude awakening if they install the update:

After installing this update, users may not be able to use the Seek Bar in Windows Media Player when playing specific files.         

The company goes on to state that it is working on a resolution and will provide fix the problem in an upcoming release. What's perhaps most worrying is that Microsoft's approach to continually update Windows 10 seems to be hitting more than a few potholes along. With the Windows 10 October 2018 Update alone, we've had a file deletion issue (which prompted pulling the update), a non-functioning iCloud app for some users, broken mapped drives, AMD and Intel driver woes, a zip file bug and other niggling concerns. Here’s a running list of issues being tracked by Microsoft.

In a separate issue, some users found that their Windows 10 Pro licenses were suddenly and mysteriously being deactivated. Microsoft later said that it would automatically resolve this issue with no intervention needed from the user. 

F1BB6CC9 183B 4CFA BB18 31BB8934FCCD

Windows 10 As A Service: that is Microsoft's mantra with regards to its current consumer operating system. However, when that "service" is constantly hobbled by self-inflected wounds, how can users consider it reliable? Microsoft fought to push back on any concerns that it may be losing its touch and penned a blog earlier this month about its commitment to quality control with Windows 10.

"Even a multi-element detection process will miss issues in an ecosystem as large, diverse and complex as Windows," wrote Michael Fortin, Microsoft Corporate VP for Windows. "While we will always work diligently to eliminate issues before rollout, there is always a chance an issue may occur.  When this happens, we strive to minimize the impact and respond quickly and transparently to inform and protect our customers."

Perhaps Microsoft should pay more attention to its unpaid Windows Insiders before releasing major updates to Windows 10. In fact, both the file deletion and zip file bugs were identified by Windows Insiders during the testing phase of the October 2018 Update (and even earlier versions of Windows 10) and were never acted upon by Microsoft until it was too late.

loadDisqus(jQuery('#initdisqus'), disqus_identifier, url);

else {
setTimeout(function () { disqusDefer(); }, 50);


function loadDisqus(source, identifier, url) {

if (jQuery("#disqus_thread").length) {


if (window.DISQUS) {

reload: true,
config: function () {
this.page.identifier = identifier;
this.page.url = url;

} else {

//insert a wrapper in HTML after the relevant "show comments" link

disqus_identifier = identifier; //set the identifier argument
disqus_url = url; //set the permalink argument

//append the Disqus embed script to HTML
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = 'https://' + disqus_shortname + '.disqus.com/embed.js';



function disqusEvent()
idleTime = 0;

Go to Source