Recently Browsing 0 members
No registered users viewing this page.
By Hamza Jawad
Power BI On-premises data gateway February update released
by Hamza Jawad
Image via Microsoft Power BI (YouTube) After wrapping up last year's Power BI updates, activity on Microsoft's data visualization and analytics platform front slowed down due to the holiday season. Today, the Redmond firm has released the latest version of the Power BI On-premises data gateway, after its last release in December introduced a new Azure Cosmos DB connector.
The first change this time around is fairly straightforward. The name of the aforementioned connector has been renamed from DocumentDB - the name it was launched with last year - to Azure Cosmos DB. This change will be visible to customers under the heading of the "data source type" in the data source settings.
The deprecation notices that were handed out with the last update are also being reiterated, as they will be coming into effect this month. For one, support for the use of gx64krb5 to undertake Kerberos single sign-on (SSO) in the process of creating SAP BW data sources is being discontinued immediately. On a similar note, support for the use of OpenSSL while creating SAP HANA data sources with SAML single sign-on is also being deprecated at the same time. Although existing connections will be supported, new ones cannot be created now, and the CommonCryptoLib is recommended for use instead.
Moving on, the Gateway install will also require the .NET 4.8 framework in all versions starting now. As always, reports published to the Power BI Service and refreshed via the Gateway will adhere to the exact same query execution logic/run-time as in this month's Power BI Desktop version.
The Standard Mode installer for the latest version - 3000.72.6 - can be downloaded here, while the Personal Mode installer can be downloaded here.
Surface Hub starts getting Windows 10 Team 2020 Update
by João Carrasqueira
Microsoft started rolling out the Windows 10 Team 2020 Update for the Surface Hub 2S last week, starting with Germany and the Netherlands. The update spread to Hub 2S users globally starting yesterday, and today it's time for the original Surface Hub to get the update.
The update is available for both the 55- and 84-inch models of the original Surface Hub, as long as you have enabled full telemetry on the device. Right now, the update will be available in a few countries, including Australia, New Zealand, Japan, Canada, Mexico, Belgium, Italy, Germany, the Netherlands, Switzerland, and UK. Starting next week, on March 2, it should be available in all markets around the world.
The update can be downloaded from Windows Update and Windows Update for Business, but you can also download the Surface Hub Recovery Tool and use it to get the update immediately. This might be the best method if you want to avoid enabling full telemetry on the device.
Microsoft notes that the update will be rolled out over the coming weeks, so it may take some time for it to show up on every device. This should help prevent any issues from spreading to every user. It's a good idea to check out the known issues with the Windows 10 Team 2020 Update before making the jump. Also, keep in mind that version 1703 will only be supported through March 16, so you shouldn't wait too long to update.
By Rich Woods
Microsoft releases Windows 10 build 19042.844 with tons of fixes
by Rich Woods
Today, Microsoft is releasing a new cumulative update for those that are on Windows 10 version 20H2 or 2004, which are currently the newest versions of the OS. This is considered to be a "C" week release (even though it's actually the D week), which means that it's optional. When you check for updates in Windows Update, you'll be given the option to take this update.
The update that you're going to get is KB4601382, and it brings the build number to 19042.844 or 19041.844, depending on if you're on version 20H2 or 2004, respectively. You can manually download it here, and these are the highlights:
Here's the full list of fixes:
There's also one other fix, which is exclusive to 20H2:
There are also two known issues to be aware of:
Symptoms Workaround System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.
Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps.
If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment.
Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options.
We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually.
Note The affected apps are using the ImmGetCompositionString() function.
We are working on a resolution and will provide an update in an upcoming release.
It's worth noting that Windows 10 version 21H1 is coming soon, and that's going to be an enablement package just like 20H2 was. That means that in a few months when 21H1 is out and version 1909 is no longer supported, all supported versions of Windows 10 will actually get the same updates.
As mentioned earlier, this update will arrive via Windows Update. If you choose not to take it, the fixes will be bundled into next month's Patch Tuesday update.
Microsoft releases Windows 10 build 21322 with a bunch of fixes
by João Carrasqueira
After a couple of Friday builds in the last two weeks, Microsoft is finally back on its typical Wednesday schedule for new Windows 10 builds in the Dev channel, and today, we're getting build 21322. This build comes from an active development branch that isn't tied to a specific Windows 10 update, but this time, there are no new features.
Just like most builds, though, there is a list of smaller improvements, fixes, and known issues, which you might want to check out before getting the update. First off, there are some changes, including a reversion of some new touch keyboard features due to some issues:
Next up, there's a decently long list of fixes, though there are fewer items than we've seen in the last couple of builds:
Finally, there are some known issues, and the list is still pretty extensive here:
Microsoft has also noted that some updates have been made to the Feedback Hub so that Insiders can both upvote feedback and add similar feedback to it for all categories. This should help bring each piece of feedback more attention while also providing more details on the problem or suggestion mentioned.
Since we had a shorter period between build releases this time around, it's not surprising to see fewer changes than usual and no new features at all. As we said at the start, this build isn't tied to a specific Windows 10 feature update, but at the earliest, the features in development now will show up in the 21H2 update, coming in the second half of the year. There's still quite a bit of time for features to be added and changes to be made.
By Rich Woods
Samsung reportedly releasing an Exynos-powered Windows 10 PC this year
by Rich Woods
Samsung Galaxy Book2 Samsung is no stranger to making Windows on ARM PCs, releasing devices for the most recent two generations of Qualcomm's Snapdragon Compute Platforms. But while Windows on ARM is referred to by some as Windows on Snapdragon, that phrase might not be accurate soon, as Samsung might just be working on a laptop that uses its own processor.
The report comes out of ZDNet Korea (via SamMobile), and it claims that Samsung is going to release an Exynos-powered laptop this year. It's going to come with an Exynos 2200 chipset, and even more interestingly, an AMD GPU.
Samsung and AMD have both confirmed that they were working together on a new chipset. The going assumption and rumor was that that chipset was going to be for an upcoming version of the Galaxy Z Fold. As it turns out, the two firms have completely different ambitions in mind.
As it stands right now, the only officially supported ARM processors for Windows 10 are made by Qualcomm. The only other chip vendor that's making ARM processors for PCs, obviously, is Apple, which is transitioning its Mac lineup to its custom SoCs. Indeed, compared to just a few years ago, there's a ton of competition for Intel, which is the market incumbent. AMD's Ryzen processors are better than ever, and this is the first time in years that a new architecture is supported by Windows. It would seem that Samsung is set to become another competitor for Intel.
The new Exynos-powered PC is set to arrive this year, and according to the report, it should show up in the third quarter. It's unclear, however, if Samsung is going to push the same value proposition as other ARM chip-makers. Apple is boasting performance and battery life, while Qualcomm champions its integrated cellular connectivity and fanless designs. With an AMD GPU, it's possible that Samsung could go for power.