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

Windows 10 19H1 is projected to launch in April 2019 and it is reported to feature a long list of changes and improvements. A report claims that Windows 10’s Spring 2019 update could introduce visual improvements and improved personalization setting page. Windows 10 19H1 will come with the ability to change the color of the taskbar and other elements like the tray flyout menu. Microsoft plans to update the personalization setting page to include “Choose your default Windows mode” option. The option “Choose your default Windows mode” will change the color of the taskbar and tray flyouts. It’s likely that the users will be finally able to change the taskbar color to white. “Just like the “Choose your default app mode”, there will also be a “Choose your default Windows mode” option. This should change the color of elements like the taskbar and the tray flyouts, resulting in a light shell like the ones we’ve seen on concepts in the past years,” Albatross said in a tweet. “This also means that you’ll be able to control the default shell and app modes individually”. The while or minimal look of taskbar certainly makes sense and we have seen these changes in early concepts of Windows 10. The feature is expected to arrive next year but it’s not yet available in preview builds and Microsoft hasn’t officially confirmed such reports. A more substantial overhaul of the customization options in Windows 10 is needed and users expect these options to make the operating system truly personal. There's more this and other upcoming features posted on OUR FORUM.

An internal Google Chrome page allows users to see all interstitial warnings or notifications that may be encountered while browsing the web with Chrome. An interstitial warning page is shown when Google wants to warn or notify a user about a particular risk or concern before a web page is loaded into the browser. For example, if a web page has been flagged as a phishing site, it will display the above warning before allowing you to proceed. At these warning pages, users can decide whether they want to ignore the warning and proceed or go back to the previous page they were at. While researching the recent deceptive mobile billing interstitial coming to Chrome 71, I stumbled onto the internal chrome://interstitials page that allows you to view all warnings that are supported by the particular Chrome version you are using. For example, Chrome 70 will have different warning interstitials than Chrome 71. When at this page, you can view interstitials related to SSL, SafeBrowsing, Captive Portal, and Supervised Users.  For the Safe Browsing category, you can also see normal warning pages that are shown in Chrome for mobile and desktop as well as the quieter warnings that will be displayed by Android apps using WebView. WebView is the Android platform that allows web pages to be viewed within Android apps.  The warnings for WebView are typically "quieter" than the warnings shown in Chrome browser itself. Learn more by visiting OUR FORUM.

A seeming problem with Microsoft's Windows activation servers wich caused a number of Windows 10 users to see false messages informing them they were running non-activated software. At the end of the day (U.S. Eastern time) on November 8, some users were reporting these issues were resolved. On November 8, a number of users who had activated and licensed copies of Windows 10 Pro began receiving messages saying they needed to install Windows 10 Home or go back and purchase a "genuine" copy of Windows. This included both Windows Insider testers and those builds released to mainstream users (including some users with the Windows 10 October 2018 update/1809). Some users said they had contacted Microsoft support and were told incorrectly they needed to repurchase licenses or somehow obtain new product keys. (And some people said they did this.) Some users also said they followed the instructions they received in the erroneous messages and rolled back to Windows 10 Home. Meanwhile, Microsoft officials said very little officially about what was happening. In the afternoon (ET) of November 8, after asking Microsoft for an update on the situation, I got the following message from a spokesperson: read more on our Forum

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.

 

GTranslate