and for the foreseeable so i don't know too much about this unfortunately we don't always get to research every question before we get to it but it sounds like microsoft is locking out official support of ryzen gen NUMBER_TOKEN processors from yeah windows NUMBER_TOKEN. i believe so i believe it's a situation where you can technically install it so you can get around there but you can get around it but because it's not officially supported you know there's question marks over and again we're very early in the windows NUMBER_TOKEN ecosystem so yeah i think it's hard to get unclear yeah i think it's hard for most tech channels to like as you're saying they're remaining quiet on it i mean we've got to look into it we're going to get some user reports see what the workarounds are and like how often do you look to microsoft for operating yeah yeah so i think when they say like oh it's if it's not supported it's not going to get updates i think microsoft has sort of insinuated that that might be the case in the past but then they've backflipped on that sort of thing so many times in the past it's too early to um certainly too early to get outraged we'll have to see how that one plays out but i mean i'm only just now getting caught up on actually testing windows NUMBER_TOKEN for the first time just because we've had other things by the time you watch this video i think maybe my horizon windows NUMBER_TOKEN versus windows NUMBER_TOKEN video will be at if not it will be possibly the next day or very soon i'm currently working on it as we film this i've of course done the NUMBER_TOKENth and NUMBER_TOKENth gen core series stuff and it's like yeah so far it's not really offering anything that new so i think with these things microsoft only ends up burning themselves when it comes to these issues because if they want people to use windows NUMBER_TOKEN they should be making the biggest effort they possibly can to support as many people's pcs as they can and yeah it's not like you know someone with their ryzen cpu from first gen is just going to throw it out well because it's not oh i can't run windows NUMBER_TOKEN let me just put that in the bin no they're just going to run windows NUMBER_TOKEN for as long as they possibly can if it's if it's a situation where we need to utilize like it requires a new instruction set or something from fairly recent generation cpus and that enables something that improves the user experience or whatever it may be then i'm sort of on board with that but if it's like we'll support uh iteration of this architecture yeah but we won't support the original architecture there's no real reason why we've just decided that's kind of that yeah i'm not on board with that that is dumb and unnecessary but yeah it's something we'll look into as we work through this and maybe more on it in the future NUMBER_TOKEN not NUMBER_TOKEN as you say in every single one of your videos i've been busted you've done that twice now yeah i know it's so bad anyway yeah it's a it's just whatever rolls off the tongues you don't think about it do you just say the thing by NUMBER_TOKEN
NO_SEGMENT_TOKEN