I'm going to try to avoid exact specifics here since liv is clear she doesn't want people jumping in and doing it for her, but the Pendrivelinux failure rings some ratherspecific bells (it might not be quite the same thing, but it's certainly related), and a bit of context around this may help in general - I'm aiming for "technical backstory" rather than "how-to post", not that I know the specifics of actually doing this from Windows anyway. Please do let me know if I've pitched it wrongly.
It used to be that OSes came on CD/DVDs or images that you could write to that kind of media, but that those images required some special massaging before you could boot them off USB, and these kinds of tools mostly grew up in that environment. Then people worked out how to make a "hybrid" image file that could be treated directly as either a CD/DVD image or a USB image, and would work equally well on either (it's a minor miracle that this is possible, really - it's a bit like one of those tricks where you write a single piece of source code that works in multiple programming languages). But the tools that deal with putting OS images on USB sticks either didn't catch up with the fact that they now need to do a lot less work, or they had other reasons for continuing to do that work (for example, you can usefully fiddle with an image to add persistent storage to it so that you can just always boot it from USB and never install it to your hard disk, but still keep your data around). This would be fine if the processes involved were completely reliable, but boot loaders are notoriously finicky, and in particular the syslinux boot loader has changed some of its interfaces a few times so that running the userspace installation tools from one version with the actual boot files from another version (which it's probably reading off the Ubuntu image) doesn't necessarily work.
But! Because Ubuntu images have taken this kind of hybrid approach for quite a while now, they shouldn't actually need any fancy massaging if all you want is to boot them and then immediately install to a hard disk. So one approach that's worth looking at, and certainly my default approach, is to see if you can just put the image directly on the disk without the disk creation tool trying to fiddle with the image's boot loader arrangements on your behalf. This may be a matter of turning off options in the disk creation UI, or there might be a more basic tool somewhere that does the job.
It would probably also be worth seeing if Pendrivelinux writes any log files anywhere that might be helpful for the purposes of debugging the failing case.
no subject
It used to be that OSes came on CD/DVDs or images that you could write to that kind of media, but that those images required some special massaging before you could boot them off USB, and these kinds of tools mostly grew up in that environment. Then people worked out how to make a "hybrid" image file that could be treated directly as either a CD/DVD image or a USB image, and would work equally well on either (it's a minor miracle that this is possible, really - it's a bit like one of those tricks where you write a single piece of source code that works in multiple programming languages). But the tools that deal with putting OS images on USB sticks either didn't catch up with the fact that they now need to do a lot less work, or they had other reasons for continuing to do that work (for example, you can usefully fiddle with an image to add persistent storage to it so that you can just always boot it from USB and never install it to your hard disk, but still keep your data around). This would be fine if the processes involved were completely reliable, but boot loaders are notoriously finicky, and in particular the syslinux boot loader has changed some of its interfaces a few times so that running the userspace installation tools from one version with the actual boot files from another version (which it's probably reading off the Ubuntu image) doesn't necessarily work.
But! Because Ubuntu images have taken this kind of hybrid approach for quite a while now, they shouldn't actually need any fancy massaging if all you want is to boot them and then immediately install to a hard disk. So one approach that's worth looking at, and certainly my default approach, is to see if you can just put the image directly on the disk without the disk creation tool trying to fiddle with the image's boot loader arrangements on your behalf. This may be a matter of turning off options in the disk creation UI, or there might be a more basic tool somewhere that does the job.
It would probably also be worth seeing if Pendrivelinux writes any log files anywhere that might be helpful for the purposes of debugging the failing case.