Windows XP Embedded SP3 USB Boot - Hangs on shutdown/restart

Question

Hi All,

I am using XP Embedded with SP3 and rollup update 1 for a project and am having a problem with shutdown/restart.

When I ask Windows to shutdown or restart it goes through the motions and does the shutting down windows section and then hangs up.

I have to manually reset the device to get it to boot. 

 

Hardware:

• Kontron Ai COM Express
• 2GB DDR2 RAM
• LSI HBAs
• USB 2.0 8GB Memory stick

Is this a common problem with SP3 and USB booting? Any way around this issue?

Thanks

Nathan

 

Answer 1

Take a look at point no. 12.

http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/1a4a0526-b676-4ede-a5ba-07489468a148/

12. USB Boot and ACPI Uniprocessor HAL. The Problem is that with the costumized Embedded USBSTOR(B).SYS file (also the updated 5.3?.1500) causes reboot/shutdown problems. The pc/machine shutsdown all windows processes but the pc remains in powered on state. (you can't interact with the system anymore, you see the windows shutdown screen). if i replace the usbstor.sys with the normal 5512/SP3 all machine will work fine. - any explainations? and another questions is what costumizations are implementent in the EEF usbstor(b).sys file which aren't in the normal sp3 one?

---

"Mark/Propose As Answer" if you got one.

Answer 2

So have you had any luck in getting the matter resolved?

 

Thanks

Answer 3

Take a look at point no. 12.

http://social.msdn.microsoft.com/Forums/en-US/embeddedwindowscomponents/thread/1a4a0526-b676-4ede-a5ba-07489468a148/

12. USB Boot and ACPI Uniprocessor HAL. The Problem is that with the costumized Embedded USBSTOR(B).SYS file (also the updated 5.3?.1500) causes reboot/shutdown problems. The pc/machine shutsdown all windows processes but the pc remains in powered on state. (you can't interact with the system anymore, you see the windows shutdown screen). if i replace the usbstor.sys with the normal 5512/SP3 all machine will work fine. - any explainations? and another questions is what costumizations are implementent in the EEF usbstor(b).sys file which aren't in the normal sp3 one?

---

"Mark/Propose As Answer" if you got one.

---

"Mark/Propose As Answer" if you got one.

Answer 4

VERY NICE..

May I ask, what lead you to try that option?

Or did you just stumble across it?

 

Thanks for your guaidance..Worked very well but still need to digg further.

 

 

Answer 5

Hi Ray007KAI,

Seperately we were debugging the same problem on some hardware and came to the same conclusion.  The root problem is that ACPI just doesn't return back that it's shut down so the best way around it is to not use ACPI in these particular systems.  Now this problem is relatively rare, most systems will work fine.

There is one other option: this problem does not occur in Windows Embedded Standard 7.  With the same hardware on USB boot, Windows will shut down correctly. 

Hope this helps.

Brendan

Answer 6

Now this problem is relatively rare, most systems will work fine.

about 20% of tested machines had this issue.

What lead me? i was just trying out. luck and intuition - really

---

"Mark/Propose As Answer" if you got one.

Answer 7

Hi,

What we are finding and what you probably already know is that the outwardly evaluation,  the WinXP and WES2009 usbstor.sys file are different is size and naming. The file that works is only 26k and the one that doesn't is 35k and labeled "USBSTOR.SYS" while the others are in lower case. I'm working through the BIOS settings to see if that could lead to a more concrete solution for this issue. We have already Debugged WES2009 and are working on WES7, WinXPe was a option we have begun working on and also ran into this issue. Was surprised to see a post on it already and a viable work around so fast. Thanks again for your input it helped out a lot.

Best Regards

Answer 8

Hi,

I have located the problem, it is the SP3 updated component "USB boot Mass Storage Device Ver 5.12600.5512.R5512"

It has as its source file "usbstorb.sys" but has the destination target renamed to "usbstor.sys" so that's why the builds are getting the wrong file.

Hope this helps explain the problem

 

To fix this problem, you need to go into the "USB boot Mass Storage Device Ver 5.12600.5512.R5512" Files section open usbstorb.sys then select "Advance" select "DesName" string and click on the "Edit Button" in the Value box rename "usbstor.sys" to "usbstorb.sys". Click on "OK" then "Apply"  

 

 

Answer 9

This is no fix, you just trick with TD. In my case  I created a new component with later buildnummber and overwrite flag to avoid the problem, but anyway. just use the SP3 and not special designed eef file.

---

"Mark/Propose As Answer" if you got one.

Answer 10

Hi~Brendan

I have the same USB boot problem. XP 32bit SP3 with XPE 2009.

Issue：After FBA, system should reboot automatically and boot to XPE OS.

Result：It won't reboot. System hangs.

According to below "RAY007KAI said：The file that works is only 26k and the one that doesn't is 35k and labeled "USBSTOR.SYS"

I copy USBSTOR.SYS(26K) from XP SP3. And  replaced the file to XPE image builded.

Then, it can boot to XPE Image successfully.

Is that XPE OS known issue ??? Any solution?

Thanks!

Answer 11

as you can see i reported this issue in dec 2010 and in several mails with microsoft months ago.
there was never a response to this after i figured out 'the' workaround and reported it.

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 12

Hi babydollhw,

There are two versions of usbstor.sys, one that is from Windows XP and another from us that enables USB Boot.  I don't know the sizes off hand, but when you build the system you should pick the one that matches the bus used by the drive the OS is installed on.  That is the only action that's necessary.  UsbHub.sys is also part of the equation too.

Outside of that, during development we had troubles with updates overwriting the USB boot enabled version with the Windows XP version and causing problems.  This was more of a POSReady problem that was fixed in its Setup and was not necessary in XPE, but I could be wrong.  FBA may reinstall drivers that it sees as more up to date and may clobber the right one.  We haven't seen this issue in-house, so if that's the case, let me know.  You should be able to see the file size changing from pre-FBA to post-FBA. 

This could also be a servicing issue if a newer version is being downloaded and applied from Windows update, they will not distribute a USB Boot version.  We do have an updated version of USB boot drivers post-SP3, available with other Embedded Updates.

I don't think this helps, but if you let us know what you find we'll try to help.

Brendan

Answer 13

Just want to add: I tested about 40-50 different machines (80% notebooks, 20% workstations) - overall 20% have this issue. and with SP3-5512 version i never had problems anymore with any device.

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 14

Only add 2 components in TD.

1. USB BOOT 2.0(Version 5.1.2600.5512,R5512)

2. Basic Set Top Box(Version 5.1.2600.2180,R2890)

pre-FBA：usbstor.sys size is 35KB

post-FBA：usbstor.sys size is 35KB

Seems like pre or post FBA usbstor.sys size didn't change and version 5512 has the same problem.

The right usbstor.sys from XP-SP3 is 26KB. (C:\Windows\system32\drivers)

Is there anything wrong with my setting??

Thanks!

Answer 15

urgs...

I may wasn't just clear enough.
Robert is actually wrong with overwriting.

The Pre/Post-FBA Issue is nonsense.
If you use USB Boot 2.0 - you get usbstorsB.sys - thats it.
BUT this file causes the problems.

Replace it with the normal usbstor.sys from SP3. You can find it at least in your repository.

Search for usbstor.sys, look in file details for 5512 as a version string. (i think release was 2008 - sorted by date)
Create a NEW component. But in the dependencies creating this component AFTER "USB Boot 2.0" and mark the file in advanced tab to be overwritten! <- Important.

This is the easiest and most reliable way to go.
And of course adding this new component to the Image itself.

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 16

Dear Knarz：

Sorry!!

I don't understand these meaning .

1. Search for usbstor.sys, look in file details for 5512 as a version string. (i think release was 2008 - sorted by date) <== You mean search in Target Design or search by windows search function? Whether search by TD or windows, usbstor.sys version is 5.1.2600.5512. Release date is 2008.4.14

2. Create a NEW component. But in the dependencies creating this component AFTER "USB Boot 2.0" and mark the file in advanced tab to be overwritten! <- Important." <== I don't understand. If I add "USB Boot 2.0" as I mentioned before, I don't see overwritten option in advanced tab. It only has "Enable multilanguage user interface for this component"

Would you explain more details?

Very thankful.

Answer 17

1. - Windows Search (Function).

file located:
Windows Embedded Data\Repositories\{FB63649E-C453-430B-B774-07BD9B04792B}\usbstor.sys

2. - Open Component Designer
Create add/new component.
Add the usbstor.sys in Files section
Use the advanced section to set the Overwrite Flag. (FALSE to TRUE)

I guess you know how to name/create a full component with setting a repository and so on.
If you than import the Component and add it to your image you always will overwrite the usbstor(b).sys file (the usbstorB is only source name) but keep the settings from this component in your SLX.

I personaly use some kind of prefix for custom components to see my fixes in a small "scroll-"range within TD.

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 18

Knarz, thanks!

It fixes my problem ^_^

Answer 19

good to hear that i works now, but i totaly forgot to mention in detail the "Build Order Dependency" in the Component.
Add the "USB Boot 2.0" component to the new fixing component with the radio button marked with "Before my Component" than you can be always sure the image will work properly.

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 20

Hi, guys

We use WES 2009.

The system worked well on intel d510mo and loaded from usb flash.

We purchased intel dn2800mt, we built new image and found that it hangs on reboot / shutdown.

We've used your advice (replaced usbstor).

Now the system reboot fine, but it does not mount the second partition on the flash drive!

When we try to mount the partition manually, a message appears "The operation did not complete because the partition or volume is not enabled. To enable the partition or volume, restart the computer"

Do you have any ideas?

Answer 21

Is it working with the 'original' usbstor(b) version? there were some updates released but i never tested them because i never hat trouble with any second partition (we used one sometimes).

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 22

Hi All, 

I have a similar problem, but in this case I have WES2009 installed on a SATA drive. I found that the machine does not shut down if there's a USB key in the machine. Once I remove the key the machine shuts down without any problems.

Could this be caused by the similar files?

Regards,

Petrus

Answer 23

This also could be HAL related. Which one you're using?

---

Windows Embedded Developer and Scripting Guy //Germany (Preparing a blog about Windows Embedded Standard)

Answer 24

As KNARZ pointed out earlier, there are 2 versions of usbstor.sys.

If you look closely at the following components, they use differenet versions.

• USB Boot Mass Storage Device [Version 5.1.2600.5512, R5512] - usbstor.sys (36864 bytes)
• USB Boot Mass Device [Version 5.1.2600, R620] - usbstor.sys (28672bytes)  You want this one!

Disable the usbstor.sys under USB Boot Mass Storage Device [Version 5.1.2600.5512, R5512] and then build your image.  XPe will shutdown with with no issues whether the USB key in on or not as well as fix the issue where USB keys seen as a fixed disks in explorer.

Regards

Su