Intel has made available a brand new Wireless Bluetooth update developed for a number of its adapters, namely version 21.30.0 making sure users won't experience short audio distortions during Skype call, and add general stability improvements and optimizations.

In addition to that, the current release will also remove some bugs that caused problems in a few instances, removes the Yellow Bang register Device Manager after sequentially enable airplane mode, and fixes other conditions as described within the Release Notes below.

Regarding the supported hardware, the 21.30.0 version is suitable for Intel's Tri-Band Wireless-AC 17265, 18260, and 18265 adapters, as well as for the Dual Band Wireless-AC 3165, 3168, 7265, 8260, and 8265 (+Desktop Kit) models.

Moreover, the update is also compatible with the Wi-Fi 6 AX200 hardware, Dual Band Wireless-N 7265 controllers, the Wireless-AC 9260, 9461, 9462, and 9560 devices, and the Wireless-N 7260 and 7265 products.

With regards to operating systems, version 21.30.0 concentrates at 32- and 64-bit variants of Windows 7, Windows 8.1, and Windows 10 (for this administrators), as well as for Windows 10 (for end-users). However, know that not all adapters mentioned previously are supported on each OS.

So far as installation goes, the operation is straightforward: save the appropriate package ideal for the body configuration and bit variant, run it, and follow all instructions displayed for an entire and successful upgrade.

Moreover, once the installation has finished, it would be smart to perform a reboot to permit all changes to take effect properly. If this task isn't requested automatically, be sure to carry on with it manually.

Considering all aspects mentioned previously, download Intel Wireless Bluetooth Driver 21.30.0 that's valid for computer configuration, put it on, and also check our website to be aware whenever a newer version is available.

Windows 10 May 2019 Update is seemingly rolling out pretty slowly in the early stages - with Microsoft being understandably cautious and keen not to repeat any October 2018 Update-style nightmare - and perhaps as a result of this, Microsoft has decided to notify users when their PC isn't ready for that update.

Normally, if your PC isn't ripe for a feature update yet, and contains been blocked due to compatibility difficulties with your hardware components or even the software you're running, you simply won't hear anything about the upgrade.

And perhaps Microsoft has realized that this might lead to some people scratching their heads, wondering what on earth might be going on by having an update, especially in the case of a slow-paced rollout, because the May 2019 Update seems to be.

So now, at least on some machines (reported by Windows Latest), whenever you try looking in the Windows Update menu, you receive a message telling you that the device isn't quite ready for that latest feature update yet. There's also a connect to Microsoft's support site for more info, in the event you want it.

There is also a similar message through the Update Assistant tool in Windows 10, too.

This can be a useful additional touch to help keep people informed about where their machine stands with regards to the latest upgrade, and it also helps notch in the level of transparency, something which Microsoft is working to do on a broader level with regards to these major updates (with moves like an update health dashboard).

While Microsoft has been going slow with deploying the May 2019 Update, things might be accelerating now, because the company looks to make the upgrade to any PCs still running the April 2018 Update. And that's quite a number of machines, since the problematic October 2018 Update wasn't provided to nearly all users, and many folks are now simply skipping straight over it (as previously predicted).

Virtual names

Another relatively minor but interesting tweak for Windows 10 was highlighted by Bleeping Computer, although in this case, it's a possible alternation in the preview form of the OS.

It seems that users will get the choice to rename virtual desktops later on, based on the proven fact that Albacore - a Twitter user who often uncovers interesting Windows titbits, like big changes visiting Cortana - spotted a concealed feature in the latest preview build for Windows 10 20H1 (the update scheduled to land within the first half of 2020).

So rather than virtual desktops simply being called Desktop 1, Desktop 2, and so forth, you will be able to rename them to some thing meaningful, which is definitely a good touch.

As we mentioned, though, this can be a hidden alternation in the backdrop with the preview build, and the feature continues to be in development: it won't yet save the names of the rechristened virtual desktops, for example.

What this means is it could just be Microsoft playing around and testing the feature, so it may later abandon, there aren't any guarantees here. Still, it appears as though a comparatively easy switch to implement, and we see no reason why it might be ditched. Keep the fingers crossed if you're a regular virtual desktop user who would appreciate this capability.

The Windows 10 October 2018 Update has slowed down once again with regards to the pace of its rollout.

This really is according to the latest figures for April from AdDuplex, which reveal that the October 2018 Update has become running on 29.3% of PCs (as measured by the firm's ads which are displayed in Microsoft Store apps, having a sample size in excess of 100,000).

Compare that to March, when the October 2018 Update was on 26.4%, and you may observe that the increase in adoption didn't quite reach 3%. From February to March, there is a 5.2% increase in adoption from the upgrade, as well as in January, we witnessed much more of a leap of 8.8%.

So as you can observe, because the months have rolled on since the oncoming of 2019, the interest rate of adoption has gradually slowed to the level where it's back to a crawl, and also the speed it was moving finally year (when the update was famously paused to find the best a part of per month, which hardly helped things).

As always, we have to keep in mind case some sample statistics, so not really a definitive overview by any means, however it certainly paints a rather dire picture of products for Microsoft, since October 2018 Update still hasn't even reached 30% of PCs.

And with the May 2019 Update taking the baton later next month, the October 2018 Update is effectively going to exhaust road.

Missing by a mile

Previously, AdDuplex had speculated that the October 2018 Update wouldn't reach 1 / 2 of PCs prior to the next upgrade came out, and people began to jump straight to that instead. However, it seems that the October offering will barely reach another of Windows 10 machines, let alone half.

Talking about the May 2019 Update, that's already on 0.8% of PCs, which represents the ranks of testers testing out the update before its official release (that is expected to happen later in May).

Microsoft is taking its time using the May 2019 Update to ensure that it gets things right, and avoids any nasty gremlins within the works like that we witnessed using the halting from the October 2018 Update (namely a scary file deletion flaw).

And for starters that means curing the worrying obstacle that the May 2019 Update has hit with USB drives, whereby drive letters - including internal system drives - can be reassigned with potential nasty complications.

Microsoft has updated its popular Your Phone app for Windows 10, so users are now able to send MMS (Multimedia Messaging Service) messages while using app on PC.

This will allow users to send images, videos and GIFs from the app, and it's an element that many those who have used Your Phone have been waiting for.

Your Phone is a handy app for reading and replying to texts that arrive in your smartphone from within Windows 10. You can also view and edit recent photos taken on your smartphone directly on your PC, and Microsoft has promised new features to help make the app even better.

Early access

The new features are just available to people signed up to the Windows Insider program, which gives access to early versions of Windows 10 and it is apps.

To obtain the feature, you'll must have Windows 10 Build OS 18362.113 (19H1) or 18885 (20H1) or later installed.

However, should you don't want to subscribe to early version of Windows, it appears as though the updated Your Phone app could arrive when the windows are 10 May 2019 Update, that is due soon.

NVIDIA has presented a brand new Quadro graphics driver suitable for several of its GPU models, namely version R418 U6 (426.00) WHQL, which adds security updates for driver components and resolves Assimilate Scratch application crash due to a kernel exception.

When it comes to compatibility, producer has provided 3 downloadable packages directed at the 64-bit variants of Microsoft's Windows 7, 8, 8.1, and 10 os's, either desktop or notebook configurations.

Moreover, NVIDIA has also made available 2 executables produced for desktops only, which users have to install on Server 2008 R2 (64-bit), Server 2012, Server 2012 R2 (64-bit), Server 2016, or Server 2019 platforms.

Bear in mind that, for Windows 10 users, there are two packages available: a DCH (Declarative, Componentized, Hardware Support Apps) and a Standard file. To determine what executable is alright for the configuration, locate Driver Type under the System Information menu in the NVIDIA User interface.

With this thought, if you plan to apply this package, just save the proper one for your device, run it, wait because the wizard extracts all files required for the installation, and follow all instructions displayed for an entire upgrade.

Finally, once completed, it might be a good idea to perform a system reboot to permit all changes to consider effect properly. If the task isn't requested automatically through the wizard, make sure to carry on with it manually to avoid any unwanted problems.

In other words, download NVIDIA Quadro Graphics Driver 426.00, apply it to the body and enjoy the changes this latest version leads to. Also, check our website frequently to remain up to speed using the latest releases.

Google Chrome was, is, and can continue to be for a long time the world's number one browser around the desktop.

Based on third-party data from NetMarketShare, Google Chrome leads the browser software category with a share well over 65%, while rivals like Mozilla Firefox are far behind with under 10% share.

Consequently, the Google Chrome userbase is gigantic, and just like other software companies, Google relies on reports sent by its users in order to develop additional features for the browser and connect issues in the existing builds.

While users themselves can send bug reports to Google utilizing a built-in browser feature, the applying also comes with an integrated error reporting tool that can automatically send certain information towards the internet search engine when Chrome crashes.

The purpose of this feature is as simple as it could be: a computerized crash report helps Google find the issue that caused the mistake and then develop a fix based on the information it collected. Of course, the more reports pointing to the same issue, the bigger the chances this is widespread, so Google can prioritize the fix and roll it before it hits a significant number of devices.

But while these reports are extremely helpful for Google and users alike, some are worried the search giant might get access to information the company shouldn't otherwise see.

Indeed, some private information is definitely delivered to Google as part of these reports. An average crash report includes the next details, based on Google itself:
Memory associated with the crash, which may include page contents, payment information, and passwords
Your Chrome settings
Extensions you've installed
The site you were visiting during the time of the crash
Your device's operating-system, manufacturer, and model
The nation where you're using Chrome

Should you don't accept send this information to Google in a crash report, you can perfectly disable the automatic reporting. This isn't necessarily the most straightforward move to make, but a choice to turn off this behavior exists in the settings menu of Google Chrome in the following location:

Google Chrome > Settings > People > Sync and Google Services

The choice that you need to disable is called:

Help improve Chrome's features and gratifaction
Automatically sends usage statistics and crash reports to Google

However, if you allow such crash information to be delivered to Google, you can actually look into the reports yourselves. To do this, in Google Chrome type the next code in the address bar:

chrome://crashes

Obviously, this isn't necessarily something which beginners would do, and also at the same time frame, this feature only works when the automatic sending of the crash reports is enabled.

On a Windows 10 device, the dump files are stored in the following location:

%HOMEPATH%\AppData\Local\Google\Chrome\User Data\Crashpad\reports

If the feature is disabled or no crash occurred, this path might not exist, or even the reports folder could be empty.

Google explains in the online privacy policy that some information might be distributed to third parties:

"We may collect statistics to recognize webpages that load slowly. We use this information to improve our products and services, and also to give web-developers insight into improving their pages. We might share aggregated, non-personally identifiable information publicly with partners ?a like publishers, advertisers or web-developers."

The collected details are the same whatever the desktop platform, but the steps to disable the automatic reporting tool are identical. The dump files are stored in a different location depending on the operating-system.

Microsoft has mistakenly offered an interior Windows 10 build to users in the Windows Insider program ring.

Windows 10 build 18947, which hasn't passed internal validation to become pushed to insiders, was shipped via Windows Update to all rings in Microsoft's testing program.

While originally it looked like the release targeted 32-bit systems only, users on reddit claim they received the same surprising build on 64-bit machines too.

Build no more up for grabs

Microsoft explains inside a statement the blunder was caused by a so-called "configuration change" that allowed the build to be sold to external rings. Quite simply, it had been only said to be pushed to internal rings where Microsoft engineers could test this build, however it eventually made it to public testers too.

"We actively test and validate all of our preview builds internally before sharing them externally, however a configuration change allowed this build to release to multiple rings simultaneously, including external rings," the organization notes in a Microsoft Community post where additionally, it shared instructions regarding how to roll back for users who installed this build.

"We have made the required remediation within our Flighting service and have implemented additional changes to assist prevent out of this happening in the future. We apologize for just about any troubles this might have caused for affected Insiders and thank you for assistance in bringing this to our attention therefore we might make the required changes as soon as possible."

The build is not readily available for download from Windows Update, and Microsoft tells insiders to avoid setting it up, particularly if the update happens to be pending.

There's no ETA at this time regarding when a new build should ship, however i expect someone to go live next week considering that in the next couple of days Microsoft engineers could be busy fixing this blunder.

Microsoft has released a new feature for its Chromium-based browser to make it easier for users to tell when they are navigating the browser in incognito and when they aren't.

At this time, should you launch the InPrivate mode in Microsoft Edge browser, the only difference from a standard window is that it uses a dark visual style.

However with Edge also having a dark mode too, it may be hard for users to inform which window is which, so Microsoft is focusing on adding a tag in the InPrivate window to learn effectively to distinguish the browsing modes.

As reported on reddit, the most recent version of Microsoft Edge Canary already includes this InPrivate mode indicator in the status bar, also it turns up whenever you launch a browser window within the incognito mode.

Arriving Dev build of Edge within the next updates

The dark theme continues to be used, so when firing in the InPrivate Browsing mode, you're provided with a lot of what data is saved and what is not.

"When you browse InPrivate, Microsoft Edge will delete browsing info once you've closed all InPrivate tabs. While other people by using this device won't see your browsing activity, your school, workplace, and isp may still be able to," this message reads, adding that browsing history, cookies and data, passwords, addresses, and other form entries wouldn't be saved.

Exactly the same feature is projected to make its way to the Dev build of Microsoft Edge in the next little while. If you wish to try it out at this time, you have to install Microsoft Edge Canary on Windows 10 - version 77.0.226.0 or newer is required for the InPrivate tag to be displayed within the status bar.