Windows 10: Should these event entries worry me?

The BIOS in my motherboard, an Asus P6X58D Premium, does not recognize the Corsair as removable, probably becasue it uses an SSD controller. It is not available to boot from as a removable or fixed disk. Lot's of buyers have been surprised to find this out, I haven't seen a way to mark it as removable yet.
The Samsung is internal, but Windows sees it as removable. I haven't found a way around that either, that's why I'm here, because it's throwing the "Windows Portable Device" error about the Samsung. Which is why I wonder what the affect it has on the Samsung which I'm using for the system drive.

 

Hi,

It probably uses the USCSI protocol to talk to the SSD onboard controller.
You can boot from any flash drive really but only those that are seen as fixed drives can be used as a WTG device.
Other than that you can use it like any other flash drive.
Removable flash drives OTOH can be made bootable but (i.e. you can boot off them by writing the boot files on them but it will then load the Windows install off the internal drive.


So, all in all I don't quite see what the problem is with this Corsair drive but for sure in order to be seen as a bootable device in EFI/BIOS it must first be made bootable.


Quite frankly I have no clue why Windows handles the Samsung drive as a removable drive. Seems really strange to me.

Maybe someone else chimes in to enlighten us.


Cheers, *Wink

 

I'll give an example. Recently wanting to install Windows Ten Pro ISO, I tried using RUFUS and it will not even see the Corsair GTX, whether formatted or not. I've tried making Acronis bootable media on the Corsair, the program completes, but BIOS does not see it as "Removable" Research shows many others with same issue and no solution. I've also searched the Corsair website along with Google on how to mark the drive as removable with no success.
I'm unfamiliar with the abbreviations; "WTG" and "OTOH"

 

Hi,

Sorry for my use of acronyms, too much time spent on US forums I guess. OTOH : On the other hand, WTG : Windows To Go.

That can happen. It much depends on what you want Rufus to do. If you just want to create installation media from the ISO file onto the Corsair drive you actually don't even need Rufus for that. But that a different topic.
If the stick is visible in Windows and I take it is since you formatted it then there's nothing wrong with it.

Technically it is not a "removable" drive, practically it is. What you'd want is for it to show up in EFI/BIOS as a bootable drive. Provided it was created correctly, it should.

As an example, I have a Mushkin USB stick which is technically very similar to the Corsair one you have. I can use it pretty much any way I want with the added advantage that it can hold multiple partitions which ordinary flash drives can't.
I therefore use it as a Windows To Go drive, in other words it has Windows installed on it and can be booted off by sticking it pretty much any pc with a, say USB 2.0 port or faster.
Other than that it's just another usb stick.

So, I still don't understand what's so peculiar about this Corsair stick....

Cheers, *Wink

 

Thought I'd give an update. I recently built a new computer with a Gigabyte Z170X Designare motherboard and was able to use the Corsair GTX as a boot drive. It was much faster on the Gigabyte. The Asus was an early USB 3 board and even with all available updates, it wasn't that good with USB 3.

Back to the event error 219. I have the same error on the new build, but I do not have "Portable Services" in services. I have "Portable Device Enumerator Service" but it is set on manual trigger and is not running.

 

Hi,

Same old story really. This warning will show up in Event Viewer whenever the system is shut down with USB devices still attached.
On restart Windows then tries to load a driver for a USB device that's no longer present, hence the error.

That service is pretty useless to most people but since the AU update it's been set to manual making it much less intrusive.

If the error annoys you then just delete the HKEY pointing to it and avoid leaving USB devices connected during booting cycles.


Good to hear the GTX stick is now behaving as it should. Does it support UASP ?



Cheers, *Wink