| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 647 online users.
» 2 Member(s) | 641 Guest(s)
Applebot, Baidu, Bing, Google, claraolson, garioch7
|
| Latest Threads |
Hasleo Backup Suite V5.5....
Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software)
Last Post: pt58
4 hours ago
» Replies: 383
» Views: 412,872
|
“Virtual hard disk size” ...
Forum: WinToUSB (Best Windows To Go Creator)
Last Post: bacevs
4 hours ago
» Replies: 0
» Views: 9
|
Dynamic VHDX-based Window...
Forum: WinToUSB (Best Windows To Go Creator)
Last Post: bacevs
5 hours ago
» Replies: 4
» Views: 13,943
|
Unknown error while Creat...
Forum: WinToUSB (Best Windows To Go Creator)
Last Post: admin
6 hours ago
» Replies: 5
» Views: 79
|
Hasleo Backup Suite V5.5....
Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software)
Last Post: admin
8 hours ago
» Replies: 15
» Views: 14,125
|
Smart Backup Default
Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software)
Last Post: admin
Yesterday, 04:01 PM
» Replies: 15
» Views: 751
|
Send test e-mail causes G...
Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software)
Last Post: admin
11-04-2025, 10:08 AM
» Replies: 1
» Views: 153
|
Suggest A Forum Questions...
Forum: General Forum
Last Post: garioch7
11-04-2025, 03:16 AM
» Replies: 4
» Views: 305
|
File & Folder exclusions
Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software)
Last Post: admin
11-02-2025, 06:48 PM
» Replies: 9
» Views: 6,019
|
Too good to be true ?
Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software)
Last Post: admin
11-01-2025, 12:11 PM
» Replies: 20
» Views: 4,007
|
|
|
| About disk optimized tool on WTG... |
|
Posted by: Lavik - 10-13-2017, 05:26 PM - Forum: WinToUSB (Best Windows To Go Creator)
- Replies (5)
|
 |
Hello, Guys,
I built the Windows 10 WTG (Professional Edition) on external SSD (USB3.0 to SATA3) and run it for 2 months, looks everything is good.
But I confused about disk optimized tool recently, because it shows my disk is "hard disk drive" in media type, not the "solid state drive". And looks the OS treats the SSD like a traditional hard disk to do defragmentation.
So I post a thread on other forum and try to know what happened. According the replies, I guess the rough conclusion is: if you build a WTG by the built-in tools of Windows 10 Enterprise Edition, you'll see the correct media type "Solid State Drive"; if you built by WinToUSB, you'll see the "Hard Disk Drive" like me. The point is the OS may not do the right things to the SSD drive.
I don't know wether it is a correct thought, so I post here and hope to have some help.
Anyone has any idea?
Thanks a lot for any help!
PS. Sorry, I don't mean WinToUSB is bad, actually it is a very good tools and helps me to finish WTG very easily. I just have a confused problem needs to be figured out. Thanks for the team of WinToUSB！！！
|
|
|
| Application error 0xc000007b |
|
Posted by: rrussell - 10-07-2017, 03:26 AM - Forum: EasyUEFI
- Replies (3)
|
|
Hi, guys -
We're interested in using your command line utility to detect custom USB keys and automatically reboot to them from our application. It's written in C# against .NET version 4.5.2.
I've installed a "trial" of your Enterprise software.
When I run either EasyUEFI.exe *or* EasyUEFIC.exe from the command line, or using the application shortcut, everything is fine.
When I copy your EasyUEFIC.exe and supporting DLLs to our application's folder and set up a new Process to spawn for it, I get a popup saying "EasyUEFIC.exe - Application Error" and "The application was unable to start correctly (oxc000007b). Click OK to close the application." And sure enough, it quits, even before producing any sort of log.
In general, I'm doing this:
Code: System.Diagnostics.Process shellpro = new System.Diagnostics.Process();
System.Diagnostics.ProcessStartInfo startInfo = new System.Diagnostics.ProcessStartInfo();
startInfo.WindowStyle = System.Diagnostics.ProcessWindowStyle.Normal;
startInfo.WorkingDirectory = System.Environment.CurrentDirectory;
startInfo.FileName = "EasyUEFIC.exe");
startInfo.Arguments = "--list-efi";
startInfo.UseShellExecute = false;
startInfo.Verb = "runas";
startInfo.LoadUserProfile = true;
startInfo.RedirectStandardOutput = true;
startInfo.RedirectStandardError = true;
startInfo.CreateNoWindow = true;
shellpro.ErrorDataReceived += Shellpro_ErrorDataReceived;
shellpro.StartInfo = startInfo;
// this is where the error crops up.
shellpro.Start();
...
The idea is we will capture the UEFI boot devices and parse it out for our particular USB key.
I've tried it with and without "runas" and LoadUserProfile.
I've tried it changing the command to "cmd.exe" with parameters "/c EasyUEFIC.exe", and even inside a batch file.
This code was working when a coworker handed it to me, running against EasyUEFI version 1.7.0.1, but his trial license had expired and I downloaded 3.0 instead.
Running Windows Version 10.0.15063 Build 15063
Any suggestions?
|
|
|
|
|
