By continuing to use the site or forum, you agree to the use of cookies, find out more by reading our GDPR policy

Some Windows 10 users are having problems with their Pro licenses today, as users on the company's Community Forums and Reddit are reporting that their Windows 10 Pro systems are saying they are not activated, and telling users to install Windows 10 Home instead. Most of the reports appear to be coming from users who obtained the Windows 10 license thanks to the free upgrade path Microsoft offered back in 2015, suggesting that the issue is somehow related to it. According to some of the reports, while the system says that users have a Windows 10 Home license, the Microsoft Store link in the settings page blocks them from attempting to buy a Pro license. Microsoft has since acknowledged an ongoing issue with its activation servers, which is causing systems to falsely report this information, commenting that the problem should be fixed within a couple of days. Microsoft also says that the Windows activation troubleshooter may report that you have a Home license, but users are advised to ignore this message and wait for the problem to be resolved on Microsoft's side. Windows should reactivate as normal, assuming your key or digital license was genuine before all this happened. Microsoft has not yet commented officially on any of its Twitter accounts that it has been fixed, despite 27 pages and counting of complaints on its Community forums post. Visit OUR FORUM for further details.

A couple of weeks ago, Microsoft rolled out a cumulative update (KB4462933) for Windows 10 version 1803. The cumulative update was rolled out on October 24 for users who have installed Windows 10 April 2018 Update and it fixed several issues with the OS. The cumulative update came with fixes for BSOD issue which occurred while removing the Bluetooth devices from the computer along with fixing a bug which prevented the launch of Windows Defender Application Guard. The company back then not acknowledged any issues in the cumulative update but Microsoft has quietly updated the support document to confirm two bugs hitting Windows 10. Microsoft says that the cumulative update has broken the Developer Tools in Microsoft Edge. Launching this menu will no longer work on PCs with Windows 10 version 1803. The second issue which Microsoft has acknowledged is a bug that occurs after installing the August Preview of Quality Rollup or September 11, 2018, .NET Framework update. After installation, there will be an exception with the instantiation of SqlConnection. As a temporary workaround, Microsoft has detailed the points to manually resolve the issue. We have the temporary workaround posted on OUR FORUM.

A vulnerability discovered in Icecast streaming media server could be leveraged by an attacker to kill the broadcast of online radio stations that rely on it to reach their audience. The flaw is sufficient to trigger a segmentation fault in the server process - an access violation condition that leads to a crash. A theoretical risk exists for remote code execution. An attacker could achieve this with sufficiently long, specially crafted HTTP headers. Maintained by the Xiph.org Foundation, Icecast supports both audio and video data. Because it is available under a free software license and has support for open standards for communication, Icecast is a popular choice for creating an online radio station. A patch is included in the latest version of the software, whose changelog describes the issue as a buffer overflow that affects Icecast versions 2.4.0, 2.4.1, 2.4.2 or 2.4.3 "if there is a “mount” definition that enables URL authentication. The security bug stems from choosing the 'snprintf' function that redirects the data output to a buffer, over 'sprintf' to avoid buffer overflow issues by truncating the output if the buffer is not sufficiently large. Making this choice is not necessarily a safer bet when a specific condition is met. Nick Rolfe of Semmle Security Research Team says that the 'snprintf' function does not offer protection against buffer overflows "if you provide a size argument that's larger than the actual size of the buffer. "Follow this on OUR FORUM.