Sorry, probably crossed your post. Do you see Speccy graphic now?
Had run (2) mice for long time _ concurrently. Logitech G400 and Logitech Trackman Marble . Never an issue previously, but just removed Trackman so only G400 now connected.
Thanks!
That's the thing...even if you have never had any issues with some hardware before it does not mean it it will work flawlessly on every build. There could be a driver issue or something Windows internal that has changed and breaks driver compatibility.
For starters you have a lot of HardDrives in that machine. The 17xxx-series insider builds are known to have instability issues with storage devices or other storage related tasks that might or might not have anything directly to do with the physical hardware attached. If 17017 worked fine and 17025 does not, I think you should either remove anything non essential hardware from your computer, leaving only bare minimum hardware for using/testing the OS, OR report this issue to Feedback Hub and wait for next Build, skipping 17025 completely. I have sometimes had to do this for multiple builds because I could not even get as far as to a command prompt. :)
When testing insider builds with issues:
Use one Mouse, one keyboard (avoid USB input devices if you can), use one display adapter, use one HDD/SSD and only one display. Disconnect everything else, that also includes external USB devices like thumbdrives, HDDs and memory cards.
When it comes to software, only use the bare minimal that comes automatically from MS.
If you still have issues, skip to next build, and try again.
If all is working really well, one could connect more hardware and start adding 3rd-party software to the build. :)
Sometimes I have had to disable a lot of controllers/drivers in order to get Windows running smoothly.
Many thanks for reminding essentials for continuing with 'Beta' builds. I should be more cognizant but get complacent.
Will try some hardware removals, and/or wait for next build.
Thank-you for reviewing my issue !!
(edit) something may have just hit after your previous post. WD 3TB HDD presented some obscure issues in different PC, which is running 17025 nicely. Now installed in this PC and driver could well be the issue. I realize this is only one of many possible items, but something suggests removal and see what happens. THX!!
Kari
I'm attaching a screenshot of a running VM where I'm attempting to execute your dism command while booted off the install ISO and executing a shell cmd using Shift+F10 (thanks for this tip!). Please tell me how to modify the syntax of the /CheckIntergrity switch which resulted in the error 87 . I willl await your response.
Nah I jumped ahead and removed the /CheckIntergrity switch and the command completed successfully. A 1250 byte install.wim file exists in the Image directory. Do you want it? If you do I'll send the sysinfo on the VM.
Marty, I had enough time to see the screenshot to notice you had syntax error in command you were using. You edited your post and deleted screenshot, it disappeared in front of my eyes but I had enough time to notice at least one error. Please repost the screenshot for further checks.
Anyway, /CaptureDir switch only needs and accepts a drive as parameter but you had a path instead. If Windows drive when booted to Command Prompt is drive C: then only parameter for switch /CaptureDir is C: (highlighted in below example):
Code:dism /Capture-Image /ImageFile:C:\Image\install.wim /CaptureDir:C:\ /ScratchDir:C:\Scratch /name:"W10" /Compress:maximum /CheckIntegrity /Verify /Bootable
This tells DISM which drive contains the existing Windows installation we want to capture to an image (WIM) file.
In the short time before your screenshot disappeared, I noticed you had path C:\Scratch as parameter instead. DISM fails because it does not find existing Windows installation at C:\Scratch. Your screenshot showed the following command line:
Code:dism /Capture-Image /ImageFile:C:\Image\install.wim /CaptureDir:C:\Scratch /ScratchDir:C:\Scratch /name:"W10" /Compress:maximum /CheckIntegrity /Verify /Bootable
C:\Scratch should only be used as parameter for /ScratchDir switch (written in blue font in above sample).
Kari
@martyfelker OK, you reposted the screenshot. I've highlighted syntax errors:
(Click to enlarge.)
Yellow highlight: As I mentioned in my previous post, parameter for /CaptureDir can only be a drive letter followed by colon and backslash, not a folder path. You have /CaptureDir:D:\Scratch, when you should have /CaptureDir:D:\ (assuming your Windows drive is D:\ when booted to Command Prompt).
Green highlight: /CaptureDir switch is only used once. Here should be /ScratchDir:D:\Scratch instead, or whatever path to your Scratch folder.
The scratch folder is a temporary working folder for DISM, it's needed because when you boot to recovery console (Command Prompt at boot, or booting from WinPE, or booting from install media and opening Command Prompt) it's run from RAM disk X:.
When DISM captures the image, RAM disk does only offer it a 64 MB temp folder which is not enough for this task and DISM will fail if no larger Scratch / temp folder is available. That's why we need to create Scratch folder on HDD and point DISM to use it instead of small Temp folder on RAM disk.
Blue highlight: It's INTEGRITY, not INTERGRITY. Switch name should be /CheckIntegrity.
Kari
OK. I'll delete the install.wim file, reboot and try typing the command again.With the correct spelling.
OK the command is executing now. I did not set a timer but my wristwatch says I started almost exactly at 5:00 PM EST
Quote
