Replies

Alex5723 wrote:

Ascaris wrote:

When I saw the headline, I thought it meant that 64-bit Windows would not be able to run 32-bit programs

32 bit apps are next, just like Apple did with iOS and MacOS.

I’m not so sure about that, Apple care much less about backwards compatibility than Microsoft do. I can’t see them removing WOW64 anytime soon.

radosuaf wrote:

Lenovo Ideapad Miix 300 for example, Sir! Many 2GB RAM tablets still have 32-bit Windows and 32-bit drivers only.

I have one, an Acer Iconia W3. But it’s one of the infamous Clover Trail machines, so would be officially stuck on 1607. I left it on Windows 8.1 because even though it can (on paper) take 1607, the video driver is terrible so it’s not worth it. The video driver is the main reason why Microsoft locked them to 1607, they should never have been upgraded to Windows 10 in the first place.

No, no unknown devices in there. But I’ve resolved the issue with the sound at least.

I ran the HP Softpaq Download Manager and let it install anything that looked relevant. Works fine now but am still getting the Wi-Fi error.

They appear in the System event log, I’ve attached an example of each.

The laptop has 32GB of RAM and a 512GB SSD. It’s partitioned in two volumes with 100GB assigned to the OS but still 50GB free. It doesn’t seem to be memory-related either; I can experience it even at idle with less than 4GB committed, as reported by Task Manager.

The drive letter issue is irrelevant. On BIOS/MBR systems you will always see a different drive letter assignment in recovery environments because the System Reserved partition is first on the disk, and therefore assigned as C.

Changing the drive letters in the recovery session only changes them in that session, which is loaded to a RAM disk. So the changes are lost if you reboot.

I assume this only applies to Home?

On Pro you can always create a local account during setup (even with the Ethernet cable connected) by choosing Set up for an organisation and then “Domain join instead”. You don’t have to join it to a domain, it just skips the Microsoft account setup.

Option 4 is your only man really. I decided a long time ago that I don’t want Windows Update managing my drivers.

What’s probably happening here is that the Intel driver (being a generic one) has a short device ID in the INF (e.g. PCI\VEN_8086&DEV_1916) rather than a long one with a subsystem ID (e.g. PCI\VEN_8086&DEV_1916&SUBSYS_8100103C). Windows will always prioritise a driver with a long ID match over one with a short match, even if the latter is newer.

1 user thanked author for this post.

proznik

For BitLocker, I always use “used space only” mode on SSDs and only encrypt the whole disk for mechanical hard drives. The empty space will be trimmed so there’s no security issue and it ensures that the empty space is still considered empty by the SSD.

I can’t read the article but in my personal opinion, provided that you know that TRIM is working, over-provisioning isn’t needed. I’ve been using SSDs for over 10 years now and have had no problems with wearout, even my original 60GB OCZ Vertex 2 is working fine. I don’t do anything special such as limiting writes, I just use the system as normal.

You can test TRIM with the following tool. It writes a file to a specific location, logs the location of said file and then deletes it. You’re then asked to run the tool again after about 60 seconds, when you do it reads the log file and checks the sectors where the file was. If they’ve been zeroed, then TRIM is working.

https://github.com/CyberShadow/trimcheck

You need to install the Intel chipset software for your system to clear most of these devices.

1 user thanked author for this post.

GLingner

I have to agree with Elly on this one. I hate CAPTCHA with a passion. At the end of the day, all you’re doing is training Google’s self-driving car AI.

7 users thanked author for this post.

LeonW, jburk07, JohnQ2, Cybertooth, Mr. Austin, HiFlyer, Elly

I wouldn’t worry too much about the voltage. Standard DDR3 modules are rated for 1.5V. DDR3L is intended for low power devices and is designed to run at 1.35V but also must accept 1.5V to meet the specifications.

These Sagemcom routers appear to be terrible. An Irish ISP (Eir) recently started deploying them but users have found that they can’t change the IP subnet to anything other than 192.168.1.0/24, which is causing havoc for VPN users to offices with the same subnet.

Which is exactly why I always configure greenfield sites with anything other than 192.168.0.0/24 or 192.168.1.0/24, but I don’t have that luxury with inherited sites!

1 user thanked author for this post.

Nibbled To Death By Ducks

A lot of applications nowadays install into the user’s AppData folder to bypass the need for admin rights. I don’t know if it’s the case for Zoom (I’ve never used it) but definitely for Teams, and Chrome used to do it in its early days.

2 users thanked author for this post.

jburk07, Casey H

Intel never supported anything older than HD Graphics (1st gen Core i3/i5) on Windows 8 or later. In fact, they went out of their way to block installation of some of their Windows 7 drivers for the 965 and G30/G40 series on Windows 8 by adding a blank section to the INF. The driver you’re being offered is a very basic Windows 7 driver with no OpenGL support or anything so I’d definitely avoid it if everything is working fine.

1 user thanked author for this post.

AlphaCharlie

steeviebops wrote:

If it only affects 1903 and 1909 then only Server 2019 would be affected. Server 2016 is based on 1607.

Hang on (can’t seem to edit my own post). Server 2019 is based on 1809 so shouldn’t be affected either. So would only be the Core 1903 and 1909 releases in that case.