[BUG] - Task Manager network category & Data Usage not working

[Leepee]

Description

The network field of the Task Manager does not work.

Steps to reproduce

Installed a fresh copy of the latest version of Atlas, and open task manager

Expected behavior

The network field should update to show the network use of each process

Actual behavior

All entries for network show 0 Mbps

Atlas Edition

Atlas for Windows 11 23H2

Desktop information

7600X Gigabyte B650M DS3H rev. 1.0 - build in 2.5 Gbe NIC AMD 7900XT GPU

Additional content

Wonder if this is rare and caused by the 2.5gbe nic...

[brxndonroux]

i have the same problem, would like for it to work tbh

[ALxR1337]

This is the second time I’ve installed the atlas in the last year and the second time I’ve had this bug

[brxndonroux]

if the developers can reply that would be nice

[he3als]

Try enabling troubleshooting in the Atlas folder

[IWarzy]

@he3als doesn't work for me

[he3als]

Are you on v0.3.1/v0.3.2?

[IWarzy]

On v0.3.2

[Leepee]

I'm on the latest version too. This remains the only persistent bug for me.

[CodingMadness]

Agreed. Have the same issue. Version is 0.3.2 on Windows 11 23H2

[JayXTQ]

Are you on the latest version of main or the latest version on the website? If website then I'd recommend trying to reproduce on the latest artifact instead.

[Leepee]

Are you on the latest version of main or the latest version on the website? If website then I'd recommend trying to reproduce on the latest artifact instead.

Can you expand on this? I used the download from the website when I reinstalled windows not too long ago. I'm not keen on wiping and reinstalling again, and it seems that atlas cannot be upddated.

[JayXTQ]

Yeah, that isn't the most recent version to the development standard really. When I say latest artifact I mean using the playbook based on the current last commit.

[he3als]

Hi - does this still happen in v0.4.0?

[IWarzy]

Hi - does this still happen in v0.4.0?

Hi, yes same issue for me. 🫤

[he3als]

Was this after following the documentation to reinstall? Upgrades from previous versions to v0.4.0 aren't supported.

[IWarzy]

Was this after following the documentation to reinstall? Upgrades from previous versions to v0.4.0 aren't supported.

Yes, I followed the documentation and yes, I did a clean install of Windows

[nvmiku39]

I got the same problem in v0.4.0

[nvmiku39]

win11 23H2

[spix18]

Hi - does this still happen in v0.4.0?

yes , its happening to me too, clean install 0.4.0

[Zahrun]

I am also interested to know how to fix this. As a workaround, I use the Resource Monitor, one of the Window's Administrative Tools, to display the network usage by process.

[spix18]

I am also interested to know how to fix this. As a workaround, I use the Resource Monitor, one of the Window's Administrative Tools, to display the network usage by process.

my workaround was clean install Ghost Specter, no regret atm, more mature and optimized for gaming

[Ast3risk-ops]

I am also interested to know how to fix this. As a workaround, I use the Resource Monitor, one of the Window's Administrative Tools, to display the network usage by process.

my workaround was clean install Ghost Specter, no regret atm, more mature and optimized for gaming

Congrats, you've just installed more dangerous spyware.

Ghost spectre is a malware-laden piece of trash, you're better off using stock at that point.

[spix18]

I am also interested to know how to fix this. As a workaround, I use the Resource Monitor, one of the Window's Administrative Tools, to display the network usage by process.

my workaround was clean install Ghost Specter, no regret atm, more mature and optimized for gaming

Congrats, you've just installed more dangerous spyware.

Ghost spectre is a malware-laden piece of trash, you're better off using stock at that point.

i beg to differ.

[JayXTQ]

Asterix is correct about GS being malware.

[he3als]

This issue is still relevant, but it's hard to track down as it seems to break after a random amount of time after applying Atlas. I tried to fix it for v0.4.0, but I couldn't find a root cause in time.

It's a priority for this to be fixed for the next release.