Re: Immagine Iso Windows 10
Tanja Freeze
We use TeamViewer to remote to a computer offsite and then use Windows Remote Assistance to help staff at that remote site as we don't have TeamViewer installed on all computers. Prior to installing Windows 10 1903 we had no issue using remote assistance. Since updating to 1903, windows remote assistance no longer works. Receive msra.exe bad image error noting C:\Program Files (x86)\TeamViewer\tv_x64.dll is not designed to run on windows or contains an error. We receive no errors with RDP only MSRA
We actually updated from windows 7 professional to windows 10 and the problem resolved itself. We are having another problem now where we with calibrate everything and it works fine for a little while then all of a sudden everything will be out of alignment by an inch or so.
Having the same problem. Just got the new 8MP LB cam running on win 10 (1909) i can see the camera in device manager. in the Microsoft camera app i can view the camera no problem. made sure in the privacy the LB is allow to use the camera. in LB the camera is on default settings but i have just a black image.
First post & haven't built a system in 11 years, many cobwebs to shack out. The build went great and I loaded the latest version of Windows 10 pro (fully updated). I downloaded the latest AMD Graphics Drivers recommended for my CPU (AMD Auto Detect) and received the following message after loading the drivers - "RadeonSoftware.exe - Bad Image c:\Windows\SYSTEM32\atiadlxx.dll is either not designed to run Windows or it contains an error. Try installing the program again [I did and failed] etc., etc. Error status 0xc000012f.
I'm not sure how to go forward from here. Should I try the 21.8.2 drivers - even though they are considered "optional"? The release notes do not make mention on this error/fix though. I have run into no other errors. In the meantime, the Windows Graphics Driver seems to be running just fine - but who wants to use the Windows driver?
3-Disconnect the internet from your PC to prevent Windows Update from installing a different AMD Driver and delete the created installation folder at C:\AMD to prevent any conflict with the new AMD driver installation.
4-Now run DDU in Safe Mode (Best option) or from your Desktop. Once DDU finishes uninstalling the current AMD Driver and boots back up into Windows Desktop you should now be using MS Basic Display Adapter as your Graphics driver in Device Manager.
But if your computer is working fine and the Ram is not listed on the QVL List, then most likely it is listed on the RAM manufacturer's website for being compatible with your processor and motherboard. IF not listed on the RAM Manufacturer website then just keep an eye for any type of RAM issues due to not being fully compatible if it should occur in the future.
I also see you installed the latest BETA BIOS for your motherboard. I personally would skip installing BETA BIOS unless I have no other choice to fix an issue due to BIOS. BETA BIOS can sometimes be rather buggy at times is the reason why.
Well, I gave it a good shot and I appreciated the thorough response. I followed the steps to the letter plus attempting a couple of variations - to no avail. After following the steps and installing AMD Graphics Adrenalin 21.6.1 (WHQL), I received the "blue screen" repeatedly. The options being either Troubleshoot or Restart, again.
Also is the RAM Memory modules you have installed on your motherboard's QVL List for the 5000 Series APU processors as being compatible or listed at the RAM Memory's Manufacturer Support as being compatible with your motherboard: -B550-TOMAHAWK#support-mem-22
Did your desktop unexpectedly restart and display VHD_BOOT_INITIALIZATION_FAILED error in the screen? If the same occurs it means you encounter BSOD which commonly also leads to frequent freezing of Windows 10. This is one of the most vulnerable issues and Microsoft identified it with respective bug check value. Like many others, the code for this one is 0x0000012F. Experts are with a view that it represents the phenomena of initialization failure when a user performs boot from VHD.
So it probably isn't your APU. I would check the RAM Memory and also run in a elevated Command Prompt - SFC /scannow to check your Windows OS for corruptions or missing Windows core files.
After DDU in safe mode without network, deactivate Windows Update, deactivate BIOS quick start and set the PCI Express from Auto to Gen 3 or 4. Then install the Radeon driver. With me all drivers run fine in Windows, only in the game Valhalla the 21.6.1 is so far without problems, the newer ones not.
Those modules supposedly are compatible with my APU/motherboard combination. However, my system will only run stable if I back down the speed from 4000 MHz to 2400 MHz -- acceptable in the short term, but not for the long term. The shame here is that the windows basic graphics driver runs stable at the higher 4000 MHz level.
So, for now, the AMD graphics drivers 21.8.2 are running fine at the lower clock speeds. Hopefully, an update will solve this?! Your suggestions are getting me there and are greatly appreciated. BTW - I did run the SFC command a few days ago with no errors showing.
If you have done this already then I suggest you open a MSI Support ticket and see if your Motherboard needs to be RMAed and checked if it is defective since you do have compatible RAM installed from the QVL List.
I don't overclock anything unless I know exactly what I am doing since you can damage the hardware being Overclocked. But like you I also manually overclocked my RAM from SPD speed to the speed rated by the RAM I have, 3600Mhz.
In my case I just needed to change a couple BIOS Settings to accomplish it. In my Asus Motherboard BIOS I can choose various speeds for RAM memory. So I selected 3600Mhz and then under FCLK which is 50% slower than the RAM Speed I inputted 1800Mhz. I have had no issues so far.
If for some reason you input incorrect data when Overclocking, BIOS will generally catch it and revert to the SPD speed automatically until you input the correct parameters for Overclocking the RAM. But still you can still input incorrect parameters but not enough for BIOS to reject it but then you will have all types of RAM issues when you boot into Windows.
You are right about the A-XMP -- I enabled that and it should have set up a "safe" maximum clock profile. Indeed, it set up 4000MHz -- then, crash & burn. Per your idea, I will try and play with the FCLK setting since I did notice that option in the MSI BIOS. What can go wrong?
Real World Note: Since Windows Vista, there is no technical requirement to create reference images in order to deploy Windows. After all, the ISO that you download from Microsoft contains WIM images that are in a deployable state. The main reason for creating reference images, meaning images with one or more applications in them, is often just deployment speed, and to some extent network efficiency (WIM images are highly compressed). However, in a world with better and better peer to peer solutions, better networking, better hardware, you can make deployments go quite fast even without a reference image. While more and more organizations are moving to use a thin image, and deploy settings and applications at deployment time instead, if you still need a reference image. Here is how to create one.
Due to how aggressive Windows 11 is regarding updating its native applications, which is known for breaking Sysprep, make sure the virtual machine does not have Internet access during the build and capture process.
Tip: Daniel Barras (thank you), commented about a solution I was not aware of, removing the need for blocking Internet access. Please see the discussion in the comments section. The use of state.ini reduces some cleanup options you may want to to do. Also, thanks to Steyrs for providing the below steps:
MDT can be installed either on a file server, or on your own laptop, but in this scenario, I use a file server named MDT01. Deployment of Windows 11 21H2 is only supported using Windows ADK for Windows 11 21H2, that supports both Windows 10 21H2 and Windows 11 21H2, but in my testing I found it working well even on older version of Windows ADK, like the Windows ADK 2004.
2. Once the deployment share is created you also want to relax the security a bit. MDT locks it down to hard by default. Use the following PowerShell script (named Set-MDTBuildLabPermissions.ps1) to set some better permissions (modify script to fit your environment):
Note: In my environment the MDT01 server is joined to a domain, and my service account used for the deployments is VIAMONSTRA\MDT_BA. If using a different domain, or if using a workgroup server for your build and capture modify the Set-MDTBuildLabPermissions.ps1 script to reflect that.
In this example you add Microsoft 365 Apps for enterprise (formerly named Microsoft Office 365 ProPlus) to MDT. Use the Office Deployment Toolkit (ODT) to create a package of Microsoft 365 Apps for enterprise before continuing with these steps.
To configure the deployment settings, you modify the two rules files (Bootstrap.ini and CustomSettings.ini). You can do the either via the MDT Build Lab deployment share properties, or directly in the file system, in the E:\MDTBuildLab\Control folder. Below you find the configurations I used in this guide.
Per the state.ini contributors of this post, Daniel and Steyrs, the state.ini file should be copied to the C:\Windows\setup\state folder during deployment. The state.ini file should look like this per Daniel example:
[State]
ImageState=IMAGE_STATE_SPECIALIZE_RESEAL_TO_OOBE
If you happen to be putting Notepad++ in your images, be warned that version 8.5 and up install a UWP package that will cause Sysprep to fail. The registry key and state.ini will get around the error when capturing, but the image won't deploy correctly.
I've had no issues doing a build and capture of Windows 11 23H2 in MDT as long as it's a Hyper-V Gen 1 (BIOS-based) VM, and Internet access has been blocked during the build and capture process. Here is a simple way to do that: -internet-access-to-a-hyper-v-vm/
d3342ee215