Connect with us

Windows

Surface Pro 3 tips: reset before Windows 10

blank

Published

on

how-to-install-windows-10-on-surface-pro-3

Windows 10 is here and everybody who is a Windows fan is already finding themselves trying to install the free upgrade that Microsoft is providing over the air. As it always is with software, there are people and devices out there that encounter various problems before, during or after the installation of Windows 10 and find themselves browsing Google or Bing to find an easy solution for their problems. Unfortunately, with software, it’s never as easy as one hoped, especially when it comes to the Microsoft Surface Pro 3 Windows 10 installation.

Many Surface Pro 3 owners encountered various errors when trying to install Windows 10 or their machines were bricked by an update sent out at the end of July with the purpose of prepping the device for the Windows 10 upgrade. Unfortunately, Microsoft did not directly address these issues with smaller updates and fixes as of yet, so those who have found themselves with bricked Surface Pro 3 devices still have to find another way of getting their convertibles up to date and running. For those fortunate enough to have waited a bit before giving the ok to the Windows 10 installation can now take one more precautionary step before upgrading.

The best way to upgrade to Windows 10 on a Surface Pro 3 is a clean install. By clean install I’m referring to a factory reset, which is a bit inconvenient for those not rooted in the OneDrive automatic backup system or haven’t used other methods to back their data up. Nonetheless, doing the factory reset on the Surface Pro 3 before installing Windows 10 is a very good idea that could prevent problems from surfacing during the installation or after.

According to popular belief, Windows 10 and the Surface Pro 3 make an awesome match thanks to the multitude of compatibility features that Microsoft included in the OS. At the same time, Surface Pro 3 drivers are working flawlessly thanks to Ninite and Driver Agent, which seem to be working much better than any other driver installer on a Windows system. Many users who have done the factory reset and upgraded to Windows 10 after report that their drivers were installed automatically and they haven’t discovered any flaws or errors during or after the process, which is a rarity nowadays, regardless of software provider.

One of the most common errors people who tried installing Windows 10 on Surface Pro 3 encountered, documented magnificently by Ed Tittel from the IT Knowledge Exchange community of TechTarget, is a blue screen error that occurs due to a faulty driver update that was installed previously. This small hiccup that has pretty unfortunate consequences (Windows 10 can’t be installed) can be easily fixed with a factory reset of the Surface Pro 3. Although the whole reset, update and installation process will most likely take several hours, it’s worth it, because you will be left with a stable, working, super-fast convertible device up to date with everything that Windows 10 has to offer.

But the factory reset solution for the Surface Pro 3 isn’t handy in the above situation exclusively, as other errors that you may encounter are also bypassed through the process. For example, users who find themselves in a restart loop upon installation of Windows 10 can opt for the factory reset and avoid having to send their device to a service or to warranty. Those who have faulty downloads or overheating problems will also be saved by the factory reset, even though it brings forth a loss of data many aren’t happy with. Nonetheless, I would recommend every Surface Pro 3 user who is having trouble with drivers, updates and Windows 10 installations do a factory reset. It will save much more things than it damages in the long run.

As part of the editorial team here at Geekreply, John spends a lot of his time making sure each article is up to snuff. That said, he also occasionally pens articles on the latest in Geek culture. From Gaming to Science, expect the latest news fast from John and team.

Software

Microsoft employees inadvertently disclosed confidential credentials in a security breach

blank

Published

on

blank

Microsoft has successfully addressed a security breach that made internal business information and credentials accessible to the public internet.

Researchers Can Yoleri, Murat Özfidan, and Egemen Koçhisarlı from SOCRadar, a cybersecurity firm specializing in identifying security vulnerabilities, have uncovered an accessible and publicly available storage server on Microsoft’s Azure cloud service. This server was found to contain confidential internal data pertaining to Microsoft’s Bing search engine.

The Azure storage server had code, scripts, and configuration files that stored passwords, keys, and credentials used by Microsoft workers to access internal databases and systems.

However, the storage server lacked password protection, rendering it accessible to everyone on the internet.

According to Yoleri’s statement to , the data that was leaked has the potential to assist unscrupulous individuals in identifying or gaining access to other locations where Microsoft keeps its confidential information. According to Yoleri, if the storage sites are identified, it might lead to more serious data leaks and potentially endanger the services being used.

The researchers reported the security breach to Microsoft on February 6, and Microsoft took measures to protect the leaked files on March 5.

The duration of the cloud server’s exposure to the internet is unknown, as is whether anyone other than SOCRadar found the exposed data. Upon receiving an email, a representative from Microsoft declined to make a comment at the time of publishing. Microsoft did not provide information regarding whether it has reset or altered any of the compromised internal credentials.

This incident represents the most recent security lapse at Microsoft as the corporation endeavors to regain the confidence of its customers following a sequence of cloud security breaches in recent times. Last year, researchers discovered a security breach where Microsoft employees were inadvertently revealing their own corporate network login credentials in code that was made public on GitHub.

Last year, Microsoft faced criticism when it acknowledged its lack of knowledge of the methods used by China-backed hackers to get an internal email signature key. This key granted the hackers extensive access to the Microsoft-hosted inboxes of high-ranking U.S. government officials. An independent panel of cyber experts tasked with looking into the email breach came to the conclusion last week that a number of security flaws at Microsoft allowed the hackers to succeed.

Microsoft declared in March that it was actively defending against a persistent cyberattack by Russian state-sponsored hackers. These hackers managed to pilfer sections of Microsoft’s source code and internal communications belonging to the company’s executives.

Continue Reading

Android

Telegram launches a global self-custodial crypto wallet, excluding the US

blank

Published

on

blank

Telegram, with 800 million monthly users, is launching a self-custodial crypto wallet. The move will solidify its presence in the vibrant crypto community that has grown from its chat platform and may attract more people to crypto.

Telegram and TON Foundation announced TON Space, a self-custodial wallet, on Wednesday at Singapore’s Token2049 crypto conference, which draws over 10,000 attendees.

Telegram has a complicated blockchain relationship. After the SEC sued Telegram over a massive initial coin offering, the chat app abandoned its Telegram Open Network (TON) blockchain project in 2020. The Open Network Foundation (TON Foundation), founded by open-source developers and blockchain enthusiasts, supports the development of The Open Network (TON), the blockchain powering a growing number of Telegram applications, including the wallet.

The Open Platform (TOP) and TOP Labs, a venture-building division, created the TON-based wallet.

TON Space will be available to Telegram users worldwide without wallet registration in November. The U.S., which has cracked down on the crypto industry and promoted many crypto apps to geofence users, is currently excluded from the feature.

Continue Reading

Software

According to Microsoft, hackers stole its email signing key. Kind of

blank

Published

on

blank

China-backed hackers stole a digital skeleton key to access US government emails.

A China-backed hacking group stole one of Microsoft’s email keys, allowing near-unfettered access to U.S. government inboxes, due to a series of unfortunate and cascading mistakes. Microsoft revealed how the hackers pulled off the heist in a long-awaited blog post this week. Although one mystery was solved, several crucial details remain unknown.

In July, Microsoft disclosed that Storm-0558 hackers, which it believes are backed by China, “acquired” an email signing key used to secure Outlook.com accounts. The hackers broke into government officials’ Microsoft-hosted personal and enterprise email accounts using that digital skeleton key. The hack targeted unclassified emails of U.S. government officials and diplomats, including Commerce Secretary Gina Raimondo and Ambassador to China Nicholas Burns.

The hackers’ source of that consumer email signing key was unknown until this week, when Microsoft revealed the five issues that led to its leak.

Microsoft reported in its blog that a consumer key signing system crashed in April 2021. The crash created a system snapshot for analysis. This consumer key signing system is “highly isolated and restricted” from the internet to prevent cyberattacks. Microsoft was unaware that the system crash resulted in a snapshot image containing the consumer signing key #1, which they failed to detect in snapshot#2 .

The snapshot image was “subsequently moved from the isolated production network into our debugging environment on the internet connected corporate network” to determine the system crash. Microsoft confirmed its standard debugging process, but credential scanning did not detect the key in snapshot image#3.

After the snapshot image was moved to Microsoft’s corporate network in April 2021, Microsoft said the Storm-0558 hackers were able to “successfully compromise” a Microsoft engineer’s corporate account, which had access to the snapshot image’s debugging environment, which contained the consumer signing key. Microsoft said “we don’t have logs with specific evidence of this exfiltration,” but this was the “most probable mechanism by which the actor acquired the key.”

Microsoft stated that its email systems were not properly validating the consumer signing key#4, allowing access to enterprise and corporate email accounts of various organizations and government departments. The company stated that its email system would accept a request for enterprise email using a security token signed with the consumer key#5.

Mystery solved? Not quite

Microsoft’s admission that the consumer signing key was likely stolen from its systems ends the speculation that it was obtained elsewhere.

How the intruders hacked Microsoft is unknown. Jeff Jones, senior director at Microsoft, told that “token-stealing malware” compromised the engineer’s account but declined to comment.

Phishing and malicious links can spread token-stealing malware that steals session tokens. Session tokens are small files that keep users logged in without having to re-enter a password or two-factor authentication. Thus, stolen session tokens can give an attacker full access without the user’s password or two-factor code.

Last year, a teenage hacking team called Lapsus$ used malware to steal Uber employee passwords and session tokens. CircleCi was compromised in January after its antivirus software missed token-stealing malware on an engineer’s laptop. After hackers broke into LastPass’s cloud storage via a compromised developer’s computer, customers’ password vaults were breached.

How the Microsoft engineer’s account was compromised could help network defenders prevent future incidents. The engineer’s work computer or a personal device Microsoft allowed on its network may have been compromised. The real culprits for the compromise are the network security policies that failed to block the (albeit highly skilled) intruder, so focusing on an engineer seems unfair.

Cybersecurity is difficult even for corporate mega-giants with nearly unlimited cash and resources. Even if they failed, Microsoft engineers considered a wide range of complex threats and cyberattacks when designing protections and defenses for the company’s most sensitive and critical systems. Storm-0558 hacked into Microsoft’s network by chance or knowing it would find the keys to its email kingdom. It’s a reminder that cybercriminals only need to succeed once.

No analogy fits this unique breach or circumstances. It’s possible to admire a bank’s vault security while acknowledging the robbers who stole the loot inside.

It will be some time before the full extent of the espionage campaign is known, and the remaining victims whose emails were accessed are unknown. The Cyber Security Review Board, a group of security experts that analyzes major cybersecurity incidents, will investigate the Microsoft email breach and other issues “relating to cloud-based identity and authentication infrastructure.”

 

Continue Reading

Trending