Recently Browsing 0 members
No registered users viewing this page.
By Abhay V
Supposed Surface Duo 2 images leak, showing off a triple-camera array at the back
by Abhay Venkatesh
Microsoft’s first Android device, the Surface Duo, was unveiled back in 2019 and went on sale later in 2020. While the device debuted an interesting form factor, the specifications were underwhelming for its price, thanks to the dated internal and lackluster camera performance. Now, images of what is believed to be the successor to the Surface Duo have surfaced on the web.
The leak was featured on a YouTube video from ‘Tech Rat’ showing off the device and providing an interesting look at the camera array. The images suggest that the Duo 2 houses a triple-camera system, in line with what is now becoming a bare minimum in smartphones. The first-gen device shipped with just a single underwhelming 12MP unit.
Images: Tech Rat (YouTube)Zac Bowden from Windows Central also confirmed the legitimacy of these images, providing further credence to the leak. Bowden adds that the array might include an ultra-wide-angle shooter, a telephoto lens, and a standard main camera. This makes the device more potent in the photography department, possibly justifying being priced like a flagship.
In addition to the images, the leaker claims that the device will be largely similar in dimension to that of its predecessor. However, there might be a larger display thanks to smaller bezels, housed in a device that sports a more rounded frame. The leaker also claims that the Redmond firm will add an NFC chip to the dual-screened phone, something that was absent on the original device. The folks over at Windows Central also seem to believe that the Duo 2 will feature flagship specs, such as a Snapdragon 888 SoC, which will also bring support for 5G. As for colors, the firm might be readying a black color option along with the Duo’s white color, with both the devices sporting a frosted back glass.
The addition of the camera array also seems to introduce a camera bump that might hinder the ability of the device to fold flat. It will be interesting to see if the device features a workaround for this, or if the company chooses function over form. It is also not clear whether the phone in the leaked images is an earlier prototype, and if the design has been tweaked since.
Microsoft is expected to launch the Surface Duo 2 sometime in September or October. With the first-gen Duo still running Android 10, it is anybody’s guess what the Duo 2 will ship with in terms of software. There is also no word on what the price of the Duo 2 will be.
By Steven P.
This Windows Hello webcam with privacy shutter is 20% off for only $67.99
by Steven Parker
Today on Amazon, you can pick up the wo-we Windows Hello Face Recognition Webcam for only $67.99 when you apply the $20 coupon, saving you 17% off the $84.99 list price.
A nice thing about this webcam is not only is it a cheap way into Windows Hello password-less sign-in on Windows, but also has a manual privacy shutter, something you don't get on the more than doubly expensive Logi Brio webcam.
Here are a few of its highlights:
Below are a few of this camera's specifications, besides being compliant with Windows Hello.
This item qualifies for free delivery, and the prices mentioned here are before taxes. It also includes standard manufacturer's warranty for which Amazon says you need to contact the seller.
Get the wo-we Windows Hello Face Recognition Webcam for $67.99 (list price $84.99) 20% off
As an Amazon Associate, Neowin may earn commission from qualifying purchases.
Hands-on with the new Microsoft Teams experience for Windows 11
by Anmol Mehrotra
Earlier this week, Microsoft released another Windows 11 build to Windows Insiders in the Dev Preview ring. The new build brought improvements to the UI as well as the new Microsoft Teams integration. Microsoft announced the Teams integration at the Windows 11 launch event last month. With the feature now rolling out to Windows Insiders, we decided to take a closer look at the new Teams integration for Windows 11.
First time setup
After you install the new Windows 11 build, you will see a Teams icon on the taskbar. Clicking on the option will open Team for the first-time setup. The setup is pretty simple.
Microsoft allows you to use your regular MSA account for personal use. You can also use your work or school account if you have one and want it easily accessible.
Once you select the account, Microsoft will ask you to verify ownership (if you have two-factor authentication) as well as add a phone number. This will add as a secondary username and also allow others to find you on Teams.
Lastly, Microsoft will confirm the settings and ask you if you want to use your existing Outlook or Skype contact list to find people on Microsoft Teams. One thing to note here is that if you have used Windows Phone in the past or you use Outlook to sync your contacts then you will see your address book on Teams (provided you selected the sync Outlook contact list on the last step).
Using the app
The experience is same more or less. However, with a personal Teams account, users can now use it as way to stay connected to their loved ones. Moreover, you can now enter an email address to send a Teams message to them.
This works in two parts: if the person already uses Teams, they will get a general chat notification. However, if the person you are messaging does not use Teams, they will get an email inviting them to join Teams and continue the chat.
One thing that I personally believe can enhance the Teams experience is the support for SMS. While you can message people using phone numbers, they have to be in your contacts. Unfortunately, you can’t directly start a conversation with someone if they are not in your contacts. This is something that Microsoft can add in the future to allow users to start conversations by just entering the phone number of the person they want to talk to and if the person is not on Teams, they will get an invite to join the app.
However, there is one way to invite others to a text chain and that is via the 'invite using link' option. As the name suggests, the option generates a custom link that can be shared with others to allow them to join a conversation.
Lastly, Microsoft is also expected to merge the Meet Now feature into Teams in the feature. It will further enhance the user experience by allowing users to make audio and video calls using Microsoft Teams. Currently, the feature exists just as a placeholder button, but the company is expected to add it before Windows 11 is shipped as an update to existing Windows users.
Do you plan to use Microsoft Teams on Windows 11? Let us know your thoughts below.
For more information on Windows 11, you can check out our article on minimum system requirements as well as the list of CPUs that support Windows 11. Apart from the general requirements, Microsoft has also listed out specific feature requirements for Windows 11 including webcams, Bluetooth and Precision Touchpad on all upcoming laptops. Last month, Microsoft also updated the PC Health Check app to show why a device is not ineligible to receive the Windows 11 update. However, the company will allow some manufacturers to bypass the TPM 2.0 requirement and it is also allowing Windows Insiders with unsupported hardware to test Windows 11 Insider Builds. Several manufacturers have published a list of hardware that will be compatible with Windows 11.
If you are still out of the loop, then you can check out hands-on video. If you want to get in-depth information about Windows 11 then you can check out our article covering all the new features and changes.
Microsoft Weekly: Windows 11 testing, future gaming, and HiveNightmare aka SeriousSAM
by Florin Bodnarescu
It’s been a rather busy seven days in Redmond, with new Windows 11 test builds, long-awaited game releases on console, and yet another security vulnerability all being in the news. You can find details about the aforementioned and more below, in your Microsoft digest for the week of July 18 – 24.
Windows 11 testing
It would be prudent to start with some of the news surrounding Microsoft’s next major iteration of Windows.
For one, there’s the possible release time frame, which was revealed in a document accompanying a recent Intel GPU driver update. In it, Windows 11 is referred to as the October 2021 Update, though it’s possible this may also be a reference to Windows 10 21H2, which should drop around the same time.
This timing wouldn’t be too surprising, as October has been the month of choice for the denomination or GA of several H2 updates - barring say 1809, which was quickly pulled following a number of problems, then re-released in December -, or previous major releases like Windows XP, Windows 7, and Windows 8.
As far as the release of the Long-Term Servicing Channel (LTSC) variant of Windows 11 is concerned, Microsoft was clear that it is still several years out. The LTSC release that’s about to drop this year will be based on Windows 10 21H2, but the release after that is set to be underpinned by Windows 11. Given the recent change in the LTSC support lifecycle – namely slashing of support from 10 to five years -, there’s still a bit of a wait involved.
Until then though, Microsoft is continuing to shed little more light on its Windows 11 design choices, such as the new context menu, or the Teams integration. Sadly, the Store variants for Business and Education will not be supported in Windows 11, though the downloading of Edge from the Store will be.
And speaking of, Teams chat can now be tested thanks to Windows 11 Insider build 22000.100, which also adds some taskbar enhancements. Naturally, there are some known issues to keep in mind as always, one of which is the fact that Windows Hello is now broken. Not to worry though, there’s a way to fix it.
Finally, in not exactly earth-shattering news, Microsoft has released a new cumulative update to Windows Insiders in the Release Preview ring. This is KB5004296 and should be available for folks running Windows 10 21H1 and 21H2. The only change is a new policy which „creates generic strings and removes branding-specific terms, such as „Windows” or „PC” for IoT Enterprise editions”. In other words, you’ll be seeing phrases like „Getting things ready” instead of „Getting Windows ready”.
On the gaming side of things, there’s a selection of titles now available on Game Pass, including Battlefield V, Cris Tales, Atomicorps, and Raji: An Ancient Epic. In terms of high-profile releases arriving soon, there’s Crimson Skies: High Road to Revenge, The Ascent, as well as the long-awaited console release of Microsoft Flight Simulator. If those are not your cup of tea, the Deals with Gold are right this way.
In other news of future releases, Halo Infinite’s first technical preview will focus on bots, with the kickoff allegedly happening as soon as next weekend. Matches will be 4v4 across the Bazaar, Recharge, and Live Fire maps.
Yet another first-party title, this time Fallout 76, is set to get a long-requested feature in a couple of months, namely private servers. Dubbed Fallout Worlds, it will officially arrive in the game in September, but the PTS (Public Test Servers) already have it available, for those interested in testing this out early.
Last but not least, we should mention the Dead Space remake announced at EA Play. Rebuilt by Motive Studios from the ground up to use the Frostbite engine, the game is slated to launch across PC, Xbox Series X|S, and PlayStation 5, though no release date or window was given.
HiveNightmare aka SeriousSAM
It seems like Microsoft just can’t catch a break when it comes to security recently. Following the massive Exchange Online exploits in March and April, and the PrintNightmare exploit affecting the Print Spooler Service, there’s now another high-profile security flaw going around.
Dubbed HiveNightmare – due to it being a registry vulnerability -, or SeriousSAM (due to the Windows Security Account Manager – or SAM – database being involved), the flaw allows passwords and security keys to be accessed by non-admin users. As such, it would give an attacker access to the SAM, SYSTEM, and SECURITY registry hive files. In the linked post, we’ve detailed how to restrict access to the system32 config file, as well as how to delete Volume Shadow Copy Service (VSS) shadow copies in order to protect yourself against this.
In light of the above, it’s perhaps no surprise that Microsoft chose to acquire CloudKnox Security in order to enhance its unified privileged access capabilities.
Unfortunately, the section won’t be ending with any good news, as the July set of updates for Windows 10 has broken printing and scanning via the use of smart cards. This is an unfortunate side effect of the Redmond giant’s attempts at fixing the aforementioned PrintNightmare flaw.
And as if that wasn’t enough, fake Windows 11 installers have also started circulating around the web. Unsurprisingly, they are being used for malware distribution.
Apps for Teams meetings are now supported on mobile. Microsoft is fighting legal battles to restrict the use of imposter domains. Online civility has deteriorated in the second year of the pandemic, says the Redmond giant. Edge 92 is now out, with a new Password Health dashboard. SharePoint Server Subscription Edition is now available in public preview. Visual Studio 2022 for Mac is now available in private preview. Logging off
We end today with a Task Manager concept featuring what is perhaps one of the most oft-requested features for the utility.
via AlurDesign While the Task Manager has certainly evolved over the years from its inception, one of the most often requested features is an option to switch to dark mode. Changes have been made so far in Windows 11 to make the implementation of this theme option a lot more consistent, though legacy apps still don’t respect the dark mode setting.
To visualize just how a dark mode for Task Manager would look, Twitter user Jakub (AlurDesign) has put together a concept – seen above – which makes use of the more rounded aesthetic in Windows 11, as well as translucency effects.
Of course, it’s a mere concept, but here’s hoping Microsoft sees this and chooses to take at least some design cues from it.
Missed any of the previous columns? Check them all out at this link.
If you’d like to get a daily digest of news from Neowin, we now have a Newsletter you can sign up to either via the ‘Get our newsletter’ widget in the sidebar, or this link.
Windows July update breaks printing and scanning when using smart-cards
by Sayan Sen
Microsoft seems to be having to deal with issues related to printers for a while now. This year alone, starting with the March update that caused the blue screen of death (BSOD) when trying to print, and more recently with the PrintNightmare print spooler service vulnerability. And Microsoft's troubles aren't stopping there.
Today, the firm has confirmed that its recent July security update version KB5004237, which was released on July 13, is causing problems when printing on certain systems when trying to utilize smart cards for user authentication. This time, alongside printing problems, scanning on such systems may also not work.
According to the Redmond firm, the KB5004237 July 13 cumulative update fixed printing problems on such printers that were connected via USB. However, it seems the update has also introduced a new bug as a result of the changes made for dealing with the CVE-2021-33764 vulnerability. This is causing the new issue on Domain Controller servers which act as gatekeepers responsible for dealing with such authentication requests.
It has been noted however that while working with smart cards may fail, username and password authentication should work without issue. Here's how Microsoft has described the problem:
The problem has been detailed a bit more under KB5005408 which explains that client printers and scanners must be compliant with either of the following:
Here, KDC refers to a Key Distribution Center.
The Windows platforms affected by this issue are:
Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Microsoft has said that it's investigating the issue and will provide a temporary workaround. For people having problems, the company has asked to update the necessary drivers and firmware and to consult with the device manufacturers when needed. You may find more details about the problem here on the company's official page.