Will you upgrade to Windows Live Essentials 2011 or 2012?
183 members have voted
Recently Browsing 0 members
No registered users viewing this page.
So with the upcoming releases of the new consoles, iPhone's, and GPU's I got curious as to how many of us buy it right away.
By Usama Jawad96
Poll: Which next-generation console are you interested in buying?
by Usama Jawad
The next generation of consoles is just around the corner, and we are now aware of almost all the important details including specifications, features, launch titles, value for money, pricing, and availability.
From Sony's end, we have two offerings: the PlayStation 5 and the PlayStation 5 Digital Edition. These siblings are the same in almost every aspect including a 3.5GHz octa-core AMD Ryzen Zen 2 CPU, a 10TFLOPS GPU, 16GB of GDDR6 RAM, a custom 825GB SSD, and games targeting up to 4K 120Hz video output. The only difference between the two consoles is that the standard PlayStation 5 packs an Ultra HD Blu-Ray disc drive, while the Digital Edition does not. The pre-orders situation has been messy so far, but the consoles officially launch starting on November 12 with price tags of $499 for PlayStation 5 and $399 for the PlayStation 5 Digital Edition.
Over in Microsoft's camp, the situation is quite different. We have two consoles, namely the Xbox Series X and the Series S, but both pack considerably different hardware and are intended for different audiences.
The more powerful Series X packs a 3.8GHz (3.6GHz with SMT) octa-core custom Zen 2 CPU, a 12TFLOPS GPU, 16GB of GDDR6 RAM, a custom 1TB SSD with Xbox Velocity Architecture, and games targeting up to 4K 120Hz video output. It also packs an Ultra HD Blu-Ray disc drive.
Meanwhile the less powerful Xbox Series S differs with a 3.6GHz (3.4GHz with SMT) custom Zen 2 CPU, 4TFLOPS GPU, 10GB of GDDR6 RAM, a custom 512GB SSD with the same architecture as its sibling, and games targeting up to 1440p 120Hz video output. It lacks an Ultra HD Blu-Ray disc drive as well and is meant to be an all-digital console.
Given their differing internals, the Series X is priced at $499 while the budget-friendly Series S sports a price tag of $299. Pre-orders for Microsoft's offerings start from September 22, with the consoles officially launching on November 10.
With potential customers such as Neowin readers now aware of what the tech behemoths are offering, their price tags, availability, and bang for your buck, we are interested to know: which console are you looking to buy come holiday season or later? Do you have eyes on multiple consoles rather than sticking with a single option in this generation?
Let us know by voting in the poll below (multiple options can be selected)! We're also interested to know the reasoning behind your choice so feel free to leave your thoughts in the comments section!
Here's what's new for Windows 8.1 and 7 this Patch Tuesday
by João Carrasqueira
We are now in the second Tuesday of September, and in usual Microsoft fashion, that means it's Patch Tuesday. Every supported version of Windows is getting updates today, and that includes Windows 8.1. Plus, if you're paying for extended security updates (ESU), there are new updates for Windows 7, too.
As usual, there are two flavors of the monthly updates, one containing only security fixes and one with other quality fixes, the monthly rollup update.
For Windows 8.1, the monthly rollup is KB4577066, and it can be downloaded manually here. It contains the following fixes:
It also has a single known issue that's been around for months:
Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:
Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
As for the security-only update, it's KB4577071, and it can be downloaded manually here. It only includes these updates:
It has the same known issue as the monthly rollup.
As for Windows 7, which - again - is only getting updates for paying ESU customers, the monthly rollup update is KB4577051, and it can be downloaded manually here. Here's what's changed:
The only known issue is the same as for Windows 8.1. Microsoft also notes that the update will fail to install if you don't have a valid key to receive security updates beyond the original end of support date.
As for the security-only update, it's KB4577053, and it can be downloaded manually here. It contains these changes:
It has the same known issue mentioned above.
As a reminder, the quality updates are usually automatically installed through Windows Update, but you'll need to download the security-only updates manually if you want them.
I'm running windows 7 x64.
The BSOD occured after I used a program called driver hub to update my drivers. It was going well, however after attempting to download a driver (I believe it had to do with a USB driver but I can't confirm) my computer shutdown. I restarted the computer and tried to reinstall the driver, I also got a prompt to update windows so I did that as well. My computer shutdown again but this time it loaded into a BSOD.
I've tried to boot into safe mode and it starts loading drivers but then stops and shuts down. I tried to use last know good configuration but that didn't work either. I tried to load into automatic repair mode but that didn't work, and system restore doesn't work either. I do however have access to command prompt, windows memory diagnostics, and system image recovery (although it says windows cannot find a system image on this computer)
Technical Information on blue screen:
*** STOP: 0x0000007E (0xFFFFFFFF80000003, 0xFFFFF8800194A02D, 0xFFFFF880009A9468, 0xFFFFF880009A8CD0)
*** asstahci64.sys - Address FFFFF8800194A02D base at FFFFF88001934000, Datestamp 599a919f
Information from startup repair
Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21198527
Problem Signature 05: AutoFailover
Problem Signature 06: 11
Problem Signature 07: 0x1000007e
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Diagnosis and repair details:
Root cause found:
Unknown Bugcheck: Bugcheck 1000007e. Parameters = 0xffffffff80000003, 0xfffff8800ad8502d, 0xfffff880033dfec8, 0xfffff880033df730.
Repair action: System files integrity check and repair
Result: Failed. Error code = 0x490
Time taken = 136422 ms
System Disk = \Device\Harddisk0
Windows directory = D:\Windows
AutoChk Run = no
Number of root causes = 1
Ask me if you need any other information.
By Usama Jawad96
Microsoft apparently just fixed a Windows security flaw first reported to it in 2018
by Usama Jawad
Microsoft fixed quite a number of bugs in this month's Patch Tuesday update, which came out last week. While it packed numerous fixes for various versions of Windows, it did draw some criticism for the handling of a security vulnerability that was reported to it by Google.
However, it appears that the Redmond giant's security woes are not yet over as a new report claims that the firm just fixed a Windows zero-day exploit that was reported to it back in 2018.
Last week, Microsoft fixed a security hole in various versions of Windows that mainly deals with the operating system's incorrect handling of file signatures. In CVE-2020-1464, the company noted that:
In a blog post on Medium, security researcher Tal Be'ery has explained that Bernardo Quintero, a manager at VirusTotal - a service owned by Google - first discovered the vulnerability being exploited back in August 2018. This exploit, internally called "GlueBall", was immediately reported to Microsoft and the findings were published in January 2019 by Quintero. Microsoft acknowledged the issue and added mitigation actions in supporting tools, but stated that it would not fix the issue in the operating system itself. The reasoning behind this decision is not public.
After this, several blog posts were published by other people, explaining how to use GlueBall to exploit Windows. Then in June 2020, GlueBall was once again highlighted by prominent social media accounts.
It would seem that roughly around this time, Microsoft began to take this issue seriously and a proper fix to the gaping security hole was finally released in this month's Patch Tuesday. According to Microsoft's security advisory, this flaw was present in Windows 7, 8, 8.1, RT 8.1, Server 2008, 2012, 2016, 2019, and Windows 10, going all the way up to version 2004, and that it was exploited across numerous versions of the operating system.
In a vague statement to KrebsonSecurity, Microsoft stated that:
The handling of this incident from Microsoft's end is extremely strange, to say the least. One has to wonder why Microsoft delayed fixing a Windows security flaw for nearly two years, especially when it was present in virtually all major versions of the operating system.
Source: Tal Be'ery (Medium) via KrebsonSecurity