Acronis Customer Expert Support Confirmed To Me That There Is An Issue With TI 2018
This is a particular issue and not at all an indictment of the product in general. So after several weeks of going back and forth with customer service and getting my question elevated several times along the way today I received a message telling me that it's not me : ) but "you." I am posting not to chastise but to ask if anyone else has run into this problem. This problem did not occur with TI 2017. When I went to create the bootable flash media I think (it's been a while now) I choose custom and not the default or simple method which I believe uses a Linux platform. I have the Windows ADK package installed and choose (I think the PE builder.) Anyway after booting the flash drive I see Picture 1. I then have to maximize the small GUI window in the middle. See Picture 2. The GUI that is the Utility bar where you access the menu and or the tools is garbled and I am not able to navigate it. This is what Support said in an email to me today:
"We acknowledge that we received the screenshots and exact issue details. Developers confirmed that this is a issue in the product. The issue is still under investigation with Developers and is planned to be fixed in the next update of Acronis True Image. Unfortunately, right now there is no fixed date for the release."
So I am curious if anyone else has run into this particular problem. Windows 10 Pro. TIA.
The Recovery media doesn't scale properly, as you know. It looks to me that you may be using a 4k monitor. The only solution is to change the default WinPE resolution to a higher value compatible with your monitor. The Acronis created WinPE does not provide this option. I recommend you use the MVP Tool to create the Recovery media. You will need to elect the option to inject System drivers during the build process. The MVP Tool uses a program called DoubleDriver to extract drivers from your system. This will include the Display driver. You will also be offered a choice of resolutions to set during the build. For all this to work, you will need the Windows ADK installed. You will also need to select the option to build from an installed ADK when you run the MVP Tool.
If it doesn't work for you the first time, it means that DoubleDrive didn't get all the files needed for the Display driver. Report back and I will walk you through the process of fixing the Display driver. I've been able to make it work with Intel, nVidia and AMD Radeon graphic adapters.
@Enchantech, @Mustang
Good calls on the screen resolution/ display. Running 3840 x 2160.
>Does the word (Recommended) follow the resolution setting you see?
Yes. See attached pic. If it is applicable running win 10 pro ver. 1703. NVIDIA Quadro M1200 driver version 382.29. FYI same OS as several months ago when TI 2017 media was created without a problem though I can not say with absolute certainty that the driver version is the same.
Late this weekend is when I have set some time aside to check out both of your reccomendations and I will report back early next week. Thanks so much.
Adding your NVIDIA driver will fix your problem. I run a 4k monitor on one of my machines at 4096 by 2160. I have built WinPE and WinRE using the advanced method of the TI media builder adding the driver to each manually and both display correctly.
I have used the MVP media builder tool to do the same and settled on a 1920 X 1080 resolution to get a satisfactory look. Any higher and the True Image window is to small and hard to read. You can set resolution once booted to the MVP WinPE media so you may find another resolution you like. Not all available resolutions will be supported by your graphics card however so it is trial and error until you hit the sweet spot.
The True Image add on package that is used in the True Image Media Builder tool scales a default resolution that works fine without the trial and error that comes with the ability to adjust resolution offered by the MVP tool.
Additionally, I run scaling at 150% vs. your 250% so that will factor in as well.
>Late this weekend is when I have set some time aside to check out both of your recomendations and I will report back early next week. Thanks so much.
I appreciate the help so I just wanted to update and inform that real life has interfered with my plans to experiment with creating new media using the MVP Tool and most likely I will not be able to revisit until next weekend. I have already downloaded the MVP Tool it but I would like to clarify. Now instead of using the Acronis menu to create the bootable media I just launch the MVP Tool and follow the instructions indicated here. Thanks so much.
Yes, the MVP tool will create that media for you. Follow the readme instructions for more details on usage. Questions post back.
In reply to Yes, the MVP tool will… by truwrikodrorow…
>Questions post back.
So I had a few minutes and I thought that I would give it a shot. I ran malwarebytes and bitdefender against the folder to see if they had any objections and both came back clean. I ran the MVP_ATIPEBuilder.exe as admin. I chose build custom 64 bit Acronis win pe. The script started to look for other installed Acronis products and only came back with True Image. I had a 16GB formatted fat 32 flash drive plugged in. I got a message "adding in some goodies" and then WHAM the script just exited out and stopped. I thought it may have been preparing something else so I waited 10 minutes and nothing. RATS. I looked in the MVP_ATIPEBuilder_v143 folder and the exe file was gone! Almost as if Bitdefender all of a sudden thought it was bad and deleted it though I got no message of the kind. Though sure enough I opened up Bitdefender and clicked on Activity and app protection and saw it there. So I am guessing that at some point Bitdefender put the brakes on running the rest of the script after "adding in some goodies" appeared. Now what. I guess I need to disable Bitdefender and try again, right? If Bitdefender did find an objection I would have thought it would have objected when i first launched the exe, file. if Bitdefender did do this what would have happened next if Bitdefender had not interfered. I would have been able to choose to add display drivers and choose what WinPE or is it WinRE that I want. Thanks for any help.
Looks like Bitdefender did indeed kick out the MVP executable. The tool uses an admin command line to do much of its work so not surprising that Bitdefender objected when it did.
Yes, had the MVP executable not been stopped you would have had opportunity to add drivers, I would go with WinPE.
So I am going to give this another go this weekend after I disable bitdefender (see problem above) however I was wondering one of the solutions (also above)
>The easiest method is to first change the resolution set for your display to a lower setting temporarily, while you create the flash media again using the Simple method which uses WinRE to create the media by default,
suggests rebuilding the media with a different screen resolution and see if that works. I currently sit at scale and layout (see pic) with 250% recommended and resolution 3840 x 2160 also recommenced. If I go this route do I need to change both settings before rebuilding the media or just one of them and what numbers should I choose? The reason I may want to go this route is that upon looking at the page (Advanced WinPE/RE Driver Injection in Acronis Media Builder) that explains how to inject the display adapter info into the bootable media that seems to require numerous steps and if it is just a simple case of changing the display temporarily that appeals to me. Also prior to reading that instructions page I thought that I might have to individually inject the drivers from say my Intel HD Graphics 630 display adapter as well as the driver from my NVIDIA Quadro M1200 but that does not appear the way to go. Any thoughts appreciated.
dan,
What size display are you using? It seems odd ot me that your scale layout set at 250% is "recommended" unless you have a very large display. I myself run a 27 inch 4k monitor at a higher than recommended resolution with a 175% scale layout. The recommended scale setting is 150% but I much prefer a 175% scale which enlarges icons, text, and app windows greater than that of a 150% scale setting. If I increase to 250% scale, icons, app windows, and text are huge, way out of proportion.
For myself I settled on a setting of 1920x1080 resolution for the Recovery Media. Scale layout will adjust itself according to resolution. Another consideration here is display aspect ratio. Is your display 16:9 or 16:10? In my case I have a 16:9 aspect ratio. Below are the various resolutions that work with these aspect ratios:
- 4:3 aspect ratio resolutions: 640×480, 800×600, 960×720, 1024×768, 1280×960, 1400×1050, 1440×1080 , 1600×1200, 1856×1392, 1920×1440, and 2048×1536.
- 16:10 aspect ratio resolutions: - 1280×800, 1440×900, 1680×1050, 1920×1200 and 2560×1600.
- 16:9 aspect ratio resolutions: 1024×576, 1152×648, 1280×720, 1366×768, 1600×900, 1920×1080, 2560×1440 and 3840×2160.
I included the 4:3 resolutions for others reading this even though it probably does not apply to you. In my case in the Windows OS I run resolution of 4096x2160 with 175% scale layout on 16:9 aspect ratio display. When it comes to Recovery Media and the True Image app plugin for that media I chose a resolution of 1920x1080 which results in a good fit for me. So in my case I have reduced screen resolution by 3 factors to achieve an acceptable functional look. Hopefully this will give you a starting point to work with. Just remember that what you see in Windows OS is not what you will see in the Recovery Media.
As for injecting drivers using the Acronis Media Builder tool you would only need to add the drivers necessary for the display adapter which is in use for the display on your machine. If this is the NVIDIA adapter then use the drivers for that and forget the Intel ones.
>What size display are you using? It seems odd ot me that your scale layout set at 250% is "recommended" unless you have a very large display.
ThinkPad P51
Part No: 20HHCTO1WW
Configuration Details
● 15.6" 4K (3840x2160), anti-glare, IPS
>It seems odd ot me that your scale layout set at 250% is "recommended"
That's what it was when I recall first looking at the settings and I just never changed it. If I was home I would take a snap of the desktop and post it. I seem to recall trying scale layout at 150% and the desktop icons were too small (I'm old) so I just reverted back to the recommended setting
>For myself I settled on a setting of 1920x1080 resolution for the Recovery Media. Scale layout will adjust itself according to resolution.
OK.I'll try that before creating the media.
>Another consideration here is display aspect ratio. Is your display 16:9 or 16:10? In my case I have a 16:9 aspect ratio.
You know I have no idea but if I had to guess it was 16:9.
>As for injecting drivers using the Acronis Media Builder tool you would only need to add the drivers necessary for the display adapter which is in use for the display on your machine. If this is the NVIDIA adapter then use the drivers for that and forget the Intel ones
Copy that. I should wind up seeing that if I follow the instructions on the web page Power User Insights: Advanced WinPE/RE Driver Injection in Acronis Media Builder,right?
I looked up the specs on your PC. Your display aspect ratio is 16:9 so trying the resolutions for a 16:9 aspect ratio will yield the best results.
Having said that, if you use the User Insights article to inject the display adapter drivers into the Acronis Media Builder tool you will not have the option to select a display resolution as you would using the MVP Media Builder tool. I know that injecting the built in Intel Graphics adapter drivers in the Acronis Media Builder tool produces an acceptable result. I do not know if same will hold true for the NVIDIA adapter. I suspect that you can possibly set which display adapter is in use in the bios settings. If so and the NVIDIA drivers do not produce an acceptable result you may have success adding the Intel Graphics adapter driver and then changing to the Intel graphics adapter in the bios prior to booting the media.
You can add both the Intel driver and the NVIDIA driver to the same media without issue. If you do that when you build the media then you can switch from one adapter to the other to see what works best providing of course that you can choose adapters in the bios.
Dan,
If you decide to try 1920 x 1080 resolution, the MVP Tool is by far the easiest way to go. The good news is that the native Microsoft Basic Display driver used in WinPE supports 1920 x 1080 resolution. You will only need to select the WinRE option that is the first question the MVP Tool asks. You will not need to select the add System drivers option as there would be no need to install a video driver. Near the end of the build you will be able to set the resolution to 1920 x 1080. Very easy, no need to even install an ADK
There are reasons why using the Acronis Media Builder won't work for you. As Bob mentioned, there is no option to select a screen resolution. You will get the default resolution of 1024 x 768. Another problem is that adding a video driver to WinPE in the normal manner as Bob has suggested doesn't work. Video drivers don't install in WinPE the same way as non-video drivers. When you install them, you are told the driver was installed successfully. However, this is not true. In reality the driver is actually just copied to the WinPE driver repository. This means that when WinPE boots you need to use a drvload command to actually install the driver from the driver repository in the running WinPE. Then you need to have a way to instruct WinPE to change the screen resolution. The MVP Tool has been designed to handle all of these task automatically. It will boot WinPE in the resolution you selected when you built it. You will also have a menu to use a program called SetRes to change the resolution. Keep in mind the highest resolution that will be available is 1920 x 1080 unless you elect to add System drivers when building the MVP Tool. That will take the video driver from your system and add it to the build. And then you will only be able to select resolutions that are supported by your video adapter and monitor
If my explanation seems complicated, that's because it is. There is no simple way to explain it. I put a lot of work into figuring this out and designing the MVP Tool to make it simple for end users.
In reply to Dan,… by truwrikodrorow…
>If you decide to try 1920 x 1080 resolution, the MVP Tool is by far the easiest way to go.
So I had some time today and went ahead and gave it another shot but unfortunately it did not go according to plan. Long story short (really) after changing the screen res to 1920 x 1080 I was curious to see what would happen if I again used the Acronis TI drop down menu and used the Media Builder. There are so many different choices I went first with Simple WinRE and that did not work and by that I mean the USB media was created but the GUI was still fracked. Tried again choosing advanced and the choices were WinPE or Linux and I chose WinPE and then I was presented with Tool Kit choices WinRE (recommended) or Win 10 using ADK and I chose WinRe and that did not work so at that point even though there were other options to try I went back to the MVP Tool (admin). For those of you keeping score you know that Bitdefender kicked me out of the script when I first tried so I went ahead and disabled Bitdefender. Screen res was still at 1920 x 1080. First option was build from installed ADK and I said yes as well as 64 bit. Option to choose res and I did the 1920 res. And there were a lot of other choices along the way none that I chose or declined that would make a difference I don't believe (BTW nice job on the script guys very easy even for me : ) to understand) and then when it was done and I rebooted and selected boot from USB well the attached pics tell the story. GUI still bad and kicking me while I was down I got an unsupported message as well. I should point out that other then the very, very messed up GUI even when I first made the initial USB several weeks ago which at the time prompted me to start this post as well as this most recent one using the MVP tool while the GUI is not readily navigable I still am able to move the mouse over where the tool bar should be and I am able to get a drop down menu. So I am not sure what I may have done wrong or what is going on and even though I would appreciate any input I may just be about over this at least for the time being. Thanks to all for the help.
Dan,
Did you see a command windows stating drvload.exe after the media you created booted? If not then your video driver did not load correctly and so your issue was not/is not solved. As Paul said the DoubleDriver app that injects the drivers in MVP tool will not add all the necessary files in some cases for video drivers.
In reply to Dan,… by truwrikodrorow…
>Did you see a command windows stating drvload.exe after the media you created booted?
You know I do not recall though I do remember hanging my head in shame when I saw the message as indicated in the pic from above that I posted,"Display mode requested and windows replied...The graphics mode is not supported" so I may have missed something on the screen. I dunno. Next weekend I am scheduled to do some back up work (I do it manually not on a "schedule") so I will first see how it goes using the fracked GUI and how difficult it might be to work like that and then see how I will proceed from there ie. trying again. I did mention that the above post was the short version of my adventure yesterday. In the attached pic below it shows the display drivers I tried to load manually during one of the attempts using the Acronis media builder and that was an adventure in and of itself. I am not at all sure I choose the correct and or all of the necessary drivers to get it to work but I think it was after that attempt I "quit" the built in media builder and went to the MVP tool.
The drvload.exe window I spoke of will display for a long enough time that you won't miss it.
Looking at your last screenshot I would suggest that if you want to try again with Acronis Media Builder tool to create media that you only add the nvlt.inf NVIDIA driver and leave out the others.
Did you find an Intel driver in your search?
Dan,
Don't give up now. You're close. I'd like you to try the MVP Tool again. This time follow the instructions in my previous post exactly. I asked you to select the WinRE option in the first question of the Tool. This is because there is a better chance of the native display driver in WinRE supporting 1920 x 1080 resolution. I think the unsupported message you got was because the native display driver in the ADK you used does not support 1920 x 1080 resolution.
If the WinRE option with the MVP Tool doesn't work, there is another step that will certainly work. It involves actually getting the display driver from your Windows system to work in WinPE. I just don't want to take all the time to explain the steps until I know the WinRE option using the MVP Tool doesn't work.
In reply to The drvload.exe window I… by truwrikodrorow…
>The drvload.exe window I spoke of will display for a long enough time that you won't miss it.
I dunno I might have missed an advert for Windows 12 2023 during the boot process of the MVP app since after I saw the note "graphics mode is not supported" I kind of tuned out a little. I could easily run it again and see if the drvload.exe window shows up but that might have to wait until later in the week as I am not home now.
>I would suggest that if you want to try again with Acronis Media Builder tool to create media that you only add the nvlt.inf NVIDIA driver and leave out the others.
Copy that. I'll give that a go next weekend.
>Did you find an Intel driver in your search?
Perhaps I should have done some more leg work but all I did was open up the driver store at C:\Windows\System32\DriverStore and looked for "intel" and the only one that I saw with the word "intel" was intel.pep which is what the I included. In retrospect that does not really look like an intel display driver but that was what I went with. See attached pic.
In reply to Dan,… by truwrikodrorow…
>Don't give up now. You're close.
: )
>I'd like you to try the MVP Tool again. This time follow the instructions in my previous post exactly.
Copy that but it might have to wait until next weekend for me to give it a go.
>I think the unsupported message you got was because the native display driver in the ADK you used does not support 1920 x 1080 resolution.
Should I uninstall the ADK package?
>If the WinRE option with the MVP Tool doesn't work, there is another step that will certainly work. It involves actually getting the display driver from your Windows system to work in WinPE. I just don't want to take all the time to explain the steps until I know the WinRE option using the MVP Tool doesn't work.
Copy that. I appreciate your time and patience!
Dan,
The Intel driver does not have Intel in the driver name. That is why the instructions in the article to add drivers to WinPE/WinRE using the Acronis Media Builder tool describe how to discover the driver name using Windows Device Manager and the pnputil command.
EDIT:
Intel graphics drivers use an OEM.inf name fortunately so what to look for in the Windows/INF folder is this OEM.inf file.
To find the OEM.inf file name use Windows Device Manager, locate the Display adapters entry, double right click on it to expand it and locate the Intel entry then, double click on the Intel entry to open the Properties window. In the Properties window click on the Details tab. In the Details window expand the Property box which by default displays Device Description, by clicking on the down looking arrow on the right side of the property box. From that list locate the Inf name entry and click on it to select it. Now look in the Value box below and make note of the oemXX.inf name.
Now go to the Windows/INF folder using the Add driver in the in the Acronis Media Builder tool, locate this oemXX.inf file, and add that to the driver list. I believe that you can add both the NVIDIA driver and the Intel driver to your next attempt to build media without problem.
The above methods fail to work because the device hardware ID's cannot be located using the OEMXX.inf files in the build process when creating the media.
Correct method for adding onboard Intel Graphics adapter drivers are as follows:
The Intel Graphics adapter drivers use a universal .inf driver file name. It is igdlh64.inf. This file is located in the C:\Windows\System32\DriverStore\FileRepository. Files here are listed in alphabetic order. Using the Acronis Media Builder Add driver feature navigate to the FileRepository folder then find the igdlh64_amd64_......... file, click to select it then click on Open in the Explorer window to add the file into the Add file window in the Acronis Media Builder tool. If you find more than one file with the same name just choose one of them as any will work.
Here is a screenshot taken from a WinPE created using the MVP Tool with the Intel graphics driver successfully installed. The resolution was set to 1920 x 1080. It is on a 23" monitor.
You can prove the Intel driver is working by asking the service associated with the driver to start. Net start igfx was input at a command prompt. You can see the system responded with the requested service has already been started. If the Intel driver was not successfully loaded, the system would have said the service name is invalid.
I was also able to set the resolution to 1920 x 1080 using the MVP Tool without adding the Intel driver. I did it with both the build from an installed ADK and build from WinRE options of the MVP Tool. That means both WinRE from my Windows 10 system and the WinPR from the Windows 10 ADK I have installed support 1920 x1080 resolution.
Enchantech,
I tried adding the Intel driver as you outlined using the Acronis Media Builder. As I expected, the driver was not loaded in WinPE. It was only copied to X:\Windows\System32\DriverStore\FileRepository. After I booted the media I asked the igfx service to start. The system responded with the service name in invalid. I thought it would be possible to manually issue the proper drvload command. However, that was not possible because the necessary inf file for the driver had been removed from the FileRepository folder by Acronis during the build. Even if it had been possible to load the driver, what good would that do. You still would need a method of telling WinPE to change the resolution on the fly.
@Enchantech
@Mustang
Been under the covers for the past few days out sick. First chance to respond. Appreciate the help. More then likely will not be able to digest and implement the help until this weekend. Thanks again.
In reply to Dan,… by truwrikodrorow…
@Mustang
@Enchantech
Been under the covers for the past few days out sick. First chance to respond. Appreciate the help. More then likely will not be able to digest and implement the help until this weekend. Thanks again.
In reply to Dan,… by truwrikodrorow…
>Correct method for adding onboard Intel Graphics adapter drivers are as follows:
The Intel Graphics adapter drivers use a universal .inf driver file name. It is igdlh64.inf. This file is located in the C:\Windows\System32\DriverStore\FileRepository. Files here are listed in alphabetic order. Using the Acronis Media Builder Add driver feature navigate to the FileRepository folder then find the igdlh64_amd64_......... file, click to select it then click on Open in the Explorer window to add the file into the Add file window in the Acronis Media Builder tool. If you find more than one file with the same name just choose one of them as any will work.
Hmm. Doing some preliminary work getting ready to try again this Sunday (possibly). I was unable to locate the igdlh64 file in the suggested location.Win 10 pro Version 1703. whaddaya think?
In reply to Dan,… by truwrikodrorow…
>Don't give up now. You're close. I'd like you to try the MVP Tool again. This time follow the instructions in my previous post exactly.
OK. This weekend I will attempt to follow your instructions to the letter. I do not believe if you mentioned when I asked if it were in my best interests to uninstall the ADK package or whether or not it was relevant to do so when following your instructions. TIA.
Dan,
It is irrelevant. When you choose the WinRE option with the MVP Tool, the ADK will be ignored.
I do have a question for you. When you set the resolution in your Windows system to 1920 x 1080, did you set scaling to 100%? If not, you should try that. That's the way it will look in WinPE as there is no option to change scaling in WinPE. Scaling will be at 100%.
In reply to Dan,… by truwrikodrorow…
>It is irrelevant. When you choose the WinRE option with the MVP Tool, the ADK will be ignored.
Thanks. Copy that.
In reply to Dan,… by truwrikodrorow…
>I do have a question for you. When you set the resolution in your Windows system to 1920 x 1080, did you set scaling to 100%? If not, you should try that. That's the way it will look in WinPE as there is no option to change scaling in WinPE. Scaling will be at 100%.
No, I did not. I do not recall if that was mentioned in the many (sorry about that) previous posts only the 1920 x 1080 number. But I will set the scaling to 100% when I try this weekend. Note: During this interim period I set the res back to 3840 x 2160 : )
In reply to Dan,… by truwrikodrorow…
>When you choose the WinRE option with the MVP Tool,
>I put a lot of work into figuring this out and designing the MVP Tool to make it simple for end users.
I must be dumber than a bag of rocks. Didn't work once again ) : I have to assume at that point this is all on me (and maybe my machine and configuration and whatever driver is doing this) since undoubtedly the MVP builder has worked for many. Just not me. So once again I successfully turned off Bitdefender, set the scale to 100% and the res to 1920 X 1080 and even rebooted to make sure it stuck. Launched MVP and selected the WinRE option. Choose 64bit media build. No to network map. This time I said no to injecting custom drivers unlike before. And at one point I choose the 1920 X 1080 res. The build continued without incident and as before told me that it was successful. I suppose somehow I am not getting the correct driver to load using the MVP tool and I seemed to screw it all up when I tried previously using the Acronis Media Builder tool and manually injecting it. Upon booting the flash drive the first message I got as before (see pic) was " Graphics mode not supported." I should emphasize and I believe I pointed this out before while the GUI is un-navigable I still am able to move the cursor and access I think all the functionality of the program (see pic).
>If the WinRE option with the MVP Tool doesn't work, there is another step that will certainly work. It involves actually getting the display driver from your Windows system to work in WinPE. I just don't want to take all the time to explain the steps until I know the WinRE option using the MVP Tool doesn't work.
You have no doubt noticed that I am in no rush with this so should you have the time and inclination sometime during the next month or so I would be curious to see if I can make this work once you explain how to do it for those of us who are not as smart as a 5th grader. I don't know if the pic of the display/ driver info helps or not but I thought that I would include it in the attached pics.
Thanks so much.
Hi Dan,
I did some further research on this. I also corresponded with @Mustang. I have discovered that the problem you are experiencing is an issue with WinPE and UEFI. The problem is that UEFI booted systems when booted to environments like WinPE use the Graphics Output Protocol (GOP) which uses the native display resolution of the attached monitor. This unfortunately cannot be changed or edited nor is it effected by the installation, or more accurately, the adding of a display driver. The problem has more to do with Scaling than it does resolution. The WinPE environment does not support application window scaling thus the issue you have persists.
Now the good news is that Microsoft has provided a FIX for this issue. That fix is available in WinPE versions of Win 10 ADK 1703 and above. This fix does not apply to the WinRE option of these latest versions of WinPE however so you MUST build a WinPE version of the media for the fix.
I realize that you previously stated that you have the 1703 version installed. So my question is have you actually tried to build a WinPE version of the TI Recovery Media? If not you should.
If you think that your version of WinPE ADK is not version 1703 or above then you can download these version HERE
When installing the downloaded ADK from the above link it is only necessary that you select the first 3 component options to install which will limit the footprint of the ADK tools installed on your computer.
You will need to uninstall the ADK currently installed on your computer in order to install a newer downloaded version. You can uninstall the ADK using Windows 10 Apps and Features.
Once you are certain that you have version 1703 or above ADK installed then use the TI Media Builder tool and build a Advanced option WinPE media without any drivers added.
Post back with your results.
Dan,
Thanks for the feedback. This problem has nothing to do with you or your level of level of knowledge. You aren't doing anything wrong. The simple fact is that you have a computer that is very difficult to deal with in a recovery environment.
I wanted you to use the WinRE option just to see if the built in display driver would support 1920 x 1080 resolution on your computer. Now we know the answer is NO. It' not your fault. Now we need to move to the next step.
I need to understand what you have there a little better. What I know is that you have a laptop with a 15.6" screen and a native resolution of 3840 x 2160. That resolution on a 15.6" screen makes everything too small at 100% scaling. Increasing the scaling to 250% make it usable. Before I can tell you what to do next, I need to understand your setup. Your Device Manager shows both an Intel and an nVidia display adapter. Is one used for the laptop screen and the other used for an externally connected monitor? If so, which adapter is for the laptop screen? Do you use an externally connected monitor? That may be your answer.
Dan,
I took a quick look at the specs for a ThinkPad P51. I looks to me like the 15.6" screen is using the nVidia display adapter. I'm guessing the Intel adapter is the build in adapter of the Intel processor. It also looks like the computer has an HDMI port to connect an external monitor. I would try booting into any of your TI recovery media and plugging in a 23" 1920 x 1080 resolution HDMI monitor to see what it looks like.
In reply to Hi Dan,… by truwrikodrorow…
2 quick reminders if you would indulge me:
1. Acronis's email to me which I posted I think in my first post: "We acknowledge that we received the screenshots and exact issue details. Developers confirmed that this is a issue in the product. The issue is still under investigation with Developers and is planned to be fixed in the next update of Acronis True Image. Unfortunately, right now there is no fixed date for the release."
2. And in the second week of Dec. when I received the Lenovo P51 one of the first things that I did (even before any updates) was to install Acronis TI 2017 (which later I received a free upgrade to 2018) and created the bootable media which at first did not go smoothly but eventually booted up and worked perfectly. See pdf attachment "called unable to boot from bootable rescue media builder True Image 2017"
Also before I began to pester you guys I had close to a dozen emails back and forth with Acronis support : )
>I did some further research on this. I also corresponded with @Mustang.
Thank you so much for taking the time and showing such interest in my "situation."
>I have discovered that the problem you are experiencing is an issue with WinPE and UEFI.
At one point Acronis advised me to switch from UEFI to Legacy and that met with disastrous results.
>That fix is available in WinPE versions of Win 10 ADK 1703 and above.
That terminology confused me a bit. I installed ADK on 01/19/2018 and according to the attached pic it shows version number 10.1.15063.0. However I came across this link below and in the first answer right below the question it talks about Windows ADK for Windows 10, version 1703:
>That fix is available in WinPE versions of Win 10 ADK 1703 and above.
So can I assume since I installed ADK in mid January that I indeed have Win 10 ADK 1703 and above?
>So my question is have you actually tried to build a WinPE version of the TI Recovery Media?
Honestly as I mentioned I had so many communications with Acronis Support and different methods to try that I can not be absolutely sure but I believe so. See attached PDF file called "Cannot Create Bootable Rescue Media." If I slog through some of their other communications I can check and see what other methods I tried.
>Once you are certain that you have version 1703 or above ADK installed then use the TI Media Builder tool and build a Advanced option WinPE media without any drivers added.
OK. So correct me if I am wrong but I believe I have the correct ADK version installed and I will try a rebuild next weekend when I can steal some time. Kindly look at my reply to @Mustang since there may be some info as well as attached files that I included. Thanks again.
The files that I have attached in this post are (1) a pic showing the ADK version installed and (2) a pdf file (unable to boot from bootable rescue media builder True Image 2017) from Support in December after I initially had trouble with TI 2017 and (3) a pdf file from Support (Cannot Create Bootable Rescue Media) when having trouble creating the bootable media with TI 2018.
In reply to Dan,… by truwrikodrorow…
Thank you so much for taking the time and showing such interest in my "situation."
>This problem has nothing to do with you or your level of level of knowledge
That is still open for debate : ) I am sure that you have but you may want to take a look at my reply to @Enchantech
>I need to understand what you have there a little better.
Please see attached file "Display Info."
>Your Device Manager shows both an Intel and an nVidia display adapter. Is one used for the laptop screen and the other used for an externally connected monitor?
Only the laptop screen has ever been used. I have never connected an external monitor. And to be honest I do not know if the Intel drivers or the nVidia drivers "drive" the display.
>If so, which adapter is for the laptop screen?
I do not know? I assume I can GOOGLE the answer to that but it will have to wait until later or I can ask the REDDIT THINKPAD community.
Thanks so much.
Dan, your Windows ADK version 10.1.15063.0 is better known as ADK 1511. You should be seeing 10.1.16299 if you have the 1709 ADK installed.
See webpage: Download and install the Windows ADK for links to download the 1709 or other recent ADK versions from the Microsoft site.
In reply to Dan,… by truwrikodrorow…
>It also looks like the computer has an HDMI port to connect an external monitor. I would try booting into any of your TI recovery media and plugging in a 23" 1920 x 1080 resolution HDMI monitor to see what it looks like.
Unfortunately I do not have an external monitor to try this with. I guess I should point out that this P51 "work station" notebook is my home computer. I realize it is overkill for what I use it for but when I looked this year at the ever increasing thinner and thinner laptops (HP and DELL come to mind) that run extremely hot and throttle back when only doing simple tasks and quite a few seem to have "coil whine" issues and the fact that quite a few of them were coming with soldered components I decided to go with the very easily big a** customizable Lenovo P51.
In reply to Dan, your Windows ADK… by truwrikodrorow…
>Dan, your Windows ADK version 10.1.15063.0 is better known as ADK 1511. You should be seeing 10.1.16299 if you have the 1709 ADK installed
Hi. Thanks for the input. When you say "1709 ADK" am I correct in assuming that the 1709 ADK package is intended for those "folks" running the Windows Fall Creators edition? I am still running win 10 1703 so should I uninstall my ADK version and choose the link for Windows ADK for Windows 10, version 1703 or does it matter and I should always be using the latest ADK version even if I am using windows 10 ver. 1703.
Thanks.
Dan, as far as I understand, you can use the 1709 ADK on any version of Windows 10 or on Windows 7 or 8.1 either. The rules may be more strict if you were doing development on the system where the ADK version should match your OS version, but for the purpose of building ATI WinPE media, it should not matter.
Dan,
You do have ADK version 1703 installed. Version 10.1.15063.0 is ADK 1703. Using the next version (1709) will not help you either.
If I were you, I would spend $100 on 1920 x 1080 HDMI monitor to save all the trouble you're going through. Why don't you go to a computer store and ask them to demo the monitor on your computer before you buy it. Boot into the recovery media and plug in the monitor. I think it will work. I use the Intel 630 video adapter you have listed in your Device Manager with a 23" 1920 x 1080 monitor and it work fine. I'm sure the laptop display is being controlled by the nVidia adapter. Why else would the Intel adapter be active unless it was being used to control the HDMI port?
Dan,
Thanks for posting back. I have to go out away from home for a good portion of the day. I will respond to you here later tonight.
We can agree that you do have Windows 1703 ADK installed from which to build WinPE. That is good. Your PDF reads that you did create a WinPE media using this version. I have some more information for you in this and will post back later today.
Dan,
A bit more investigation on my part reveals that by default your ThinkPad P51 uses the Intel integrated graphics (meaning run by the Intel chipset) commonly referred to as onboard graphics. As you know, your computer also has an NVIDIA Quadro M1200 discreet adapter for use with programs that need more GPU processing than what that of the Intel HD Graphics 630 can deliver. The NVIDIA adapter uses Optimus to automatically switch between an integrated graphics card and the Nvidia GPU. This is known as switchable graphics. You must enable this Graphics adapter switching using the installed (hopefully) NVIDIA Control Panel. I say hopefully because apparently in some cases This feature is not installed on some machines which would mean that if yours is one of them you cannot switch between graphics adapters, your default is the Intel adapter, and the respective NVIDIA driver may not be installed properly meaning that in Windows, applications would be unable to use the NVIDIA GPU.
Please see the article at this LINK for more details.
Now after reviewing the article above you may find that you are unable to access the NVIDIA Control Panel in which case you should review the link provided below for a Lenovo support Q and A about the subject and the fix for it
Because of the dependency between both these graphics adapters without having both fully working and given your attempts so far at adding I believe only the NVIDIA Graphics adapter driver and not both drivers then the switchable graphics will fail as well in the MVP tool build, or so I believe.
Since you have the Windows ADK version 1703 installed, you believe as do I that you have already built a WinPE media with that ADK and, it failed to correct the issue, then I am of the opinion that you need to build new WinPE media using the MVP tool and installing both the Intel and the NVIDIA drivers in the build. The trick is going to be to get drvload.exe to load both of these drivers and hope that the shared dll files between the Intel and the NVIDIA GPU's install properly so that things work as expected.
I will say here that there is probably a high probability that this will not work and may be why Acronis Support replied that this is an issue in the product that hopefully will be addressed in a future release.
I'm sure that Paul (@Mustang) will post again with some advice on how to move forward.
In reply to Dan,… by truwrikodrorow…
>If I were you, I would spend $100 on 1920 x 1080 HDMI monitor to save all the trouble you're going through.
Thanks for the suggestion but that is not something I wish to entertain at the moment. My small computer desk barely fits my laptop, printer, router and a cup of coffee. Seriously though I am not sure that I want to spend any money just to accommodate the software which while difficult to use in it's present state is not impossible. If I had any other use what so ever for an external monitor that might be a viable option but not at the moment.
In reply to Dan,… by truwrikodrorow…
>A bit more investigation on my part...
A BIT!! That is an extensive amount of leg work you did and I certainly appreciate it and I would not want to give you the impression that I am giving it short shrift but I will need to wait until this weekend in order to have the time to fully digest and investigate and or implement your suggestions. Thanks so much.
Full instructions for getting the Intel video driver to work with the MVP Tool:
1. Select the build from ADK option.
2. During the build, select to add System Drivers.
3. Select 1920 x 1080 resolution during the build.
4. Let the build finish. Don't boot it.
5. Open the Drivers_Extracted\x64 folder of the Tool. Drill down to the Display\Intel xxxxxx folder to see if there are files present. Now DELETE all the files leaving the folder name unchanged!
6. Look for a Display\nvidia folder. Delete the nvidia folder if present.
7. Go to C:\Windows\System32\DriverStore\FileRepository\. Scroll down in that folder to find a subfolder with a name starting with igdlh64.inf. Copy all the files in that folder to the Display\Intel xxxxxx in step 5.
8. Go back to the Display\Intel xxxxxx folder in step 5 and RENAME igdlh64.inf to custom_dd.inf. This is important!
9. Build the MVP Tool again with the ADK option. This time say NO to adding System Drivers.
10. Again select 1920 x 1080 resolution. The driver in the folder in step 5 will be added at this time.
11. Let the build finish.
12. Boot the media and see what happens. You should see a drvload command window on the screen for about 30 seconds. When it closes the resolution will change if the drive was successfully loaded.
DON'T DEVIATE FROM THESE INSTRUCTIONS!
If the driver loads, but the resolution doesn't change, your done. There will be nothing left to try except following the above instructions again if you made a mistake.
In reply to Full instructions for… by truwrikodrorow…
>Full instructions for getting the Intel video driver to work with the MVP Tool:
Thanks for the detailed instruction though I would not have time to try and implement them until this weekend. You and @Enchantech are both All Stars.
I was intrigued by your easy to follow and detailed instructions however and had a look see. See attached pics though I cannot guarantee they are being uploaded in the order I intended.
>7. Go to C:\Windows\System32\DriverStore\FileRepository\. Scroll down in that folder to find a subfolder with a name starting with igdlh64.inf
Not there. I searched the FileRepository folder as well as the Windows folder. I use Agent Ransack as my go to search tool if that matters. Windows search turned up nothing as well.
https://www.mythicsoft.com/agentransack/
A cursory Google search and I could be wrong about this is that igdlh64.inf seems to be identified as a Legacy driver and I wondered if it had been replaced by something else along the way so I did some sleuthing on my own. Just to refresh in one of my posts I show Device Manager and Display Adapters and it shows the INTEL one as well as the NVIDIA one. Drilling down the Intel driver version is identified as 22.20.16.4836. And looking at the events for the Intel Display I finally see igdlh64.inf (another pic, pic 6 to be exact.) Now I am not sure exactly how to read those events but to me they may indicate updates and the igdlh64.inf driver appears to have been installed from the factory and the date 12/08/2017 corresponds to the date I first got the computer so with or without my consent as you know when you boot up for the first time there are going to be some updates. If igdlh64.inf is indeed a Legacy driver is it conceivable that Windows determined that the Legacy driver was no longer needed and replaced it with something else which is why I was unable to locate it?
Another cursory Google search for what appears to be my installed Intel display graphics driver version identified as 22.20.16.4836 came up with this link:
So I do not know where that leaves me regarding the excellent instructions you took the time to outline for me since I am unable to locate igdlh64.inf on my system. Thanks so much.
Addendum:
So stealing from an earlier post
>I need to understand what you have there a little better.
Please see attached file "Display Info."
>Your Device Manager shows both an Intel and an nVidia display adapter. Is one used for the laptop screen and the other used for an externally connected monitor?
Only the laptop screen has ever been used. I have never connected an external monitor. And to be honest I do not know if the Intel drivers or the nVidia drivers "drive" the display.
>If so, which adapter is for the laptop screen?
I do not know? I assume I can GOOGLE the answer to that but it will have to wait until later or I can ask the REDDIT THINKPAD community.
I got some feedback from the Thinkpad Reddit community:
[–]Session_Border 2 points 1 day ago
Both of the adapters are used to drive the laptop display - they function in a hybrid mode. When you're not using anything graphic intensive, the Intel display adapter is running by itself (it's much more power efficient than the Nvidia adapter). When you open a program that requires the extra graphics power the Nvidia chip turns on and does all the heavy lifting.
PermalinkEmbedSaveReportGive GoldReply
[–]bagaudin 1 point 19 hours ago
Hi /u/phaedruspress, Can you elaborate more on the problem in relation to Acronis software? I will look into this for you.
PermalinkEmbedSaveReportGive GoldReply
[–]phaedruspress[S] 1 point an hour ago
Thanks. Make yourself a cup of coffee : )
https://forum.acronis.com/forum/acronis-true-image-2018-forum/acronis-c…
PermalinkEmbedSaveParentEditDisable Inbox RepliesDeleteReply
[–]bagaudin 1 point an hour ago
Looking at it, coffee with caramel syrup :)
PermalinkEmbedSaveParentReportGive GoldReply
[–]bagaudin 1 point 49 minutes ago
Checked with development team - there is an issue already reported in terms of your interaction with support, issue number.
The fix is currently planned for ATI 2019 and you will be contacted by our support personnel as soon as version with fix is available (your support case remains open)
______
>ATI 2019
Hmm. Let me check my calendar : )
The latest Intel drivers are showing differently in the FileRepository folder. To find it run regedit.exe and navigate to HKLM\SYSTEM\CurrentControlSet\Services\igfx. Look at the right side for ImagePath. That will give you the path to the driver in the FileRepository folder.
I installed the latest Intel Graphics 630 driver and my path is at kit126731.inf_amd64_xxxxxxxxxxxxx in the FileRepositoy folder. The driver file is still named igdkmd.sys.
Dan,
I have some bad news for you. I tried building with the latest Intel Graphics 630 driver from the FileRepository folder. Guess what. It didn't work! I've determined there are some files missing from the FileRepositry folder. The inf file is calling for 171 files. The FileRepository folder only has 168 files. To make it even worse, 4 of these files are not being called for by the inf file. That means there are really 7 files missing.
I do have a solution for you. Please check your Private Messages. To get there you need to click on My Account at the top of the forum page.
Dan,
I have good news today. I was able to download an older Intel 630 driver from Intel. Here is the link:
https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630
DO NOT install this driver in your Windows system. Doing so may break the video switching function of your laptop.
Follow the link above and click on See more at the bottom of the page. Scroll down and get version 15.45. Download the exe file not the zip file. I used a free program called 7-zip to extract the files from the downloaded exe file. Google it and get it installed on your computer. When the files extracted, there was a folder called Graphics. All the files needed for the driver to work in WinPE are in the Graphics folder. Use this folder instead of the FileRepository folder in step 7 of my instructions above. Copy all the files including the Lang subfolder. I tested it and it worked. You will know it works when you boot the MVP Tool and see a drvload window on the screen. This window will remain on the screen for about 30 seconds while the driver loads. If you don't see this, the driver did not work.