with such connection you should be getting 44MB/s. What about steam on your PC?

Originally posted by Red Star Gopnik:

with such connection you should be getting 44MB/s. What about steam on your PC?

It does get max speed

can you download to card on you pc, then stick it in deck? You can also try to get usb/c-eth adapter and connect to your router directly.

Originally posted by Ussul w+m1:

can you download to card on you pc, then stick it in deck? You can also try to get usb/c-eth adapter and connect to your router directly.

I could, yeah, but I would like to solve the actual issue as this is some kind of bug

Have you tried changing your download region in settings?

Originally posted by figmentPez:

Have you tried changing your download region in settings?

Yeah thats what I meant with the end of my OP

Originally posted by Fireman Sam:

Originally posted by figmentPez:

Have you tried changing your download region in settings?

Yeah thats what I meant with the end of my OP

Could it be your router? Maybe ask your friend to lend a connection for a download test...

My DL speeds have been blazing. It has made it a breeze to blow through tests on my library. I would try going somewhere I trust and connecting with a known hotpoint - maybe the home of someone you know and can verify their wifi speeds. This will cut isolating the problem. If you DL fine at a second location and other devices DL at your house fine then you know it is a setting either on your deck or some compatibility issue on your hotpoint. If you have the issue at the second hotpoint then it may not be a setting but a hardware fault. I would try a factory reset of the deck and then a reimage before going to RMA.

EDIT: Some users have reported issues that were fixed by switching between 2.4 and 5Ghz.

Originally posted by Hatchetforce:

My DL speeds have been blazing. It has made it a breeze to blow through tests on my library. I would try going somewhere I trust and connecting with a known hotpoint - maybe the home of someone you know and can verify their wifi speeds. This will cut isolating the problem. If you DL fine at a second location and other devices DL at your house fine then you know it is a setting either on your deck or some compatibility issue on your hotpoint. If you have the issue at the second hotpoint then it may not be a setting but a hardware fault. I would try a factory reset of the deck and then a reimage before going to RMA.

EDIT: Some users have reported issues that were fixed by switching between 2.4 and 5Ghz.

My DL speeds were also blazing for the first few days. I think I'll try factory reset after I get a dongle tomorrow to try via cable. The weirdest thing is that it really is only Steam on the Deck that has this slowness issue.

Originally posted by Fireman Sam:

Originally posted by Hatchetforce:

My DL speeds have been blazing. It has made it a breeze to blow through tests on my library. I would try going somewhere I trust and connecting with a known hotpoint - maybe the home of someone you know and can verify their wifi speeds. This will cut isolating the problem. If you DL fine at a second location and other devices DL at your house fine then you know it is a setting either on your deck or some compatibility issue on your hotpoint. If you have the issue at the second hotpoint then it may not be a setting but a hardware fault. I would try a factory reset of the deck and then a reimage before going to RMA.

EDIT: Some users have reported issues that were fixed by switching between 2.4 and 5Ghz.

My DL speeds were also blazing for the first few days. I think I'll try factory reset after I get a dongle tomorrow to try via cable. The weirdest thing is that it really is only Steam on the Deck that has this slowness issue.

I am still getting DL speeds that are crazy and mine was a first wave 512. I would go to the home of an acquaintance, verify their wifi speeds and then attempt a DL. And a factory reset or reimage, which RMA would ask you to do anyway, is preferable to sending in your Deck and waiting on a replacement.

I'd say try to download something from the internet, if the speed is good then it's something with steam servers or steam application itself

Update: its not the wifi, because it is just as slow with wired LAN and it really is only Steam.

Update 2: this might be an RMA, its the same (kinda worse tbh) after factory reset

Originally posted by Fireman Sam:

Update: its not the wifi, because it is just as slow with wired LAN and it really is only Steam.

Update 2: this might be an RMA, its the same (kinda worse tbh) after factory reset

Update 3: I was about to bring it over to a friend to try with on another network, then I had the idea to remove my Pi-hole from my network and now I download with full speed. I have no friggin idea why this caused the aforementioned issues. Now i just need to figure out what to change in the Pi-hole, cause i still wanna use that too obviously. Moral of the story: always start troubleshooting with testing in another network.

Originally posted by Fireman Sam:

have no friggin idea why this caused the aforementioned issues. Now i just need to figure out what to change in the Pi-hole, cause i still wanna use that too obviously.

I had a problem with my pihole. It runs on a zero W2. everything is fine, but sometimes other wlan devices cant reach it anymore. my solution was, that my router now uses the pihole as a dns and my devices ask as usual the router.

the other option can be that your pihole get a server that is not the fastest from your connection to reach. some ISPs use steam cache servers to reduce traffic.

Originally posted by Fireman Sam:

Originally posted by Fireman Sam:

Update: its not the wifi, because it is just as slow with wired LAN and it really is only Steam.

Update 2: this might be an RMA, its the same (kinda worse tbh) after factory reset

Update 3: I was about to bring it over to a friend to try with on another network, then I had the idea to remove my Pi-hole from my network and now I download with full speed. I have no friggin idea why this caused the aforementioned issues. Now i just need to figure out what to change in the Pi-hole, cause i still wanna use that too obviously. Moral of the story: always start troubleshooting with testing in another network.

Just great that you got it up and running properly. And yes - try another network :)