Recent content by Winuser

MS tries their best to release new builds weekly. Because they sometimes run into serious bugs they will delay a new release until the problem is fixed. It could be days or even weeks.

After reading your post I decided to run Winver to make sure Windows was up to date. I found that it was still on 26100.4349. When I checked WU I had to click on download and install for the latest CU.

Knowing that any version can run into problems, what really matters is how fast MS can release a fix. :-)

IMO all version of Windows have a possibility to fail when they get updated. In other words, no matter what version of Windows someone is running, without backups their taking unneccasary risks.

I stopped using the Canary builds as my daily OS on my main computer and went with the release version of 24H2. The reason why is because it became boring and not because of problems. I still use the Canary builds as the only OS on my old desktop and my laptop. I'm not sure why you had to do a...

I'm very disappointed with the updates that my Galaxy S22+ phone has received lately. The first problem was when the phone switched to using Gemini. I didn't know until when my wife wanted to call her sister from our car. Hey Google started to work until we got the message that the phone needed...

Now that brings back some old memories. :-)

I guess that could be a Win/Win. If it is the drive the problem would be solved and if not, they would have an extra drive. :-)

Yes I'm talking about trying the newest Intel driver if you haven't already installed it. Do you have a link to the device you considering?

I don't know if it's worth it or not to you but to me, It bugs me when I see a device driver not working. I have a USB device that I get a warning about not being recognized every time I start my one desktop. This just recently started happening. It does it in Win24H2 and the Canary build. I...

Could the drive be in the process indexing itself?

I have had brand new drives that I had to assign a drive letter to. This is the first time I had to do it with drives that I've been using and had data on them.

Do you know if a update may have disabled Automount? As far as I know, I didn't do anything that would have disable it.

You posted as I was replying to my post. Diskpart did solve my problem.

I found the solution to my problem. I ran Diskpart in a elevated command prompt. In Diskpart I ran Automount. This showed that Automount was disabled. Typing in Automount enable solved my problem. I have no clue of how or why Automount got turned off. I'm going to leave this thread posted in...