Videos not working after Windows 10 upgrade HP DV6-xxxx AMD

Ok, this was really bothering me. I upgraded from Windows 7 to Windows 10, and wouldn't you know it, some videos would work, and others would not in Edge and Chrome browsers. Couldn't figure it out. Stumbled across this page and this solved my problems. It is hit and miss for some users, but this did work for me. Follow this link and download the 32 or 64 bit version for windows 8.1.

http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspx



Edit #1: This also worked for my HP desktop that also has AMD A8 style processor.

Edit #2: the version 15.7.1 and the beta 15.8 Causes the video to STOP working. You need to find Beta version 15.6 of the AMD drivers.

How to Fix Error 80240020 While Installing Windows 10 Free Upgrade

Just a really quick potential fix for others having this issue,its quite simple. If you are noticing this happening:

Then you are like me, and Windows 10 free upgrade is not working. Here is the solution I used.


Go to C:\Windows\SoftwareDistribution\Download and delete everything inside that folder (I have already deleted it and started the Windows 10 upgrade process):

After you delete what is in the C:\Windows\SoftwareDistribution\Download folder, open up a command prompt as an administrator and type: wuauclt.exe /updatenow and hit enter.

After this, open up your windows update and you should see the download has already started.

 Enjoy Windows 10!

Dell Poweredge 1950 Import Foreign Configuration Strike F1

This could mean a few things, a drive has failed and you inserted a new drive, hopefully it was a raid other than 0 right? Or it could also be that an issue happened on a reboot and all you need to do is import the foreign configuration.

During POST Boot to the CTRL-R utility, make sure you are on the  VD Mgmt screen, highlight controller at the top-left, hit F2,  select Foreign, then select Import.

Now, if you are just wanting change drive to install a new OS for testing purposes, it is the same process, but you will need to initialize the NEW drives and create a new raid set. Do NOT, I repeat do NOT initialize the source main drives when switching back or you will lose everything. Also check the boot order of drive sequence in bios after changing back to the original drives. I was getting the F1 to reboot because something else was the 1st selection and for some reason, the system did not try to go to the second (PERC controller) for boot.

Office 2010 Error 1935

Wow! This error was a persistent error. Tried so many things to fix this. Uninstalled .net, ran a uninstall cleaner, ran a registry cleaner(three different ones) and nothing worked! I finally came across a very helpful post, Google searched Office 2010 Error 1935. Second Page (I know right, you got to be desperate to go to the second results page) and BAM! there was the EASIEST fix I have done, and this one worked for me!

*Disclaimer, this post is without warranty, etc. etc. I am not responsible for your computer crashing, or you losing all your pictures and documents, try this at your own risk.*

Step 1: Windows+R>regedit then hit enter

Step 2: Locate HKCU\Software\Microsoft

Step 3: Locate Key/s named Office and/or OfficeSoftwareProtectionPlatform (only Office was listed for me)

Step 4: Delete key/s, then reboot, install office and profit!

Again, this was my experience and this worked for me. Mileage may vary. Good luck, and happy troubleshooting!

Big thanks to Sammit over at http://sammit.net/how-to-fix-error-1935-when-installing-microsoft-office-2007-or-2010/ for posting this easy solution and saving the day!


-Oscar


Update 1: I had to disabled Ad Aware Anti-Virus as it was causing issue with installing certain programs. Ended up removing it all together and going a different route. Make sure you disable antivirus as well to see if that is the issue.

DCPROMO fails with: 'Failed to configure the service NETLOGON as requested' Server 2003

We have been working with a client on getting rid of the 2003 domain controllers. Came across one domain controller that wouldn't demote. Ran dcpromo and got this:

The operation failed because:

Failed to configure the service NETLOGON as requested

The reason for my clients failure was because the primary DNS server was the server itself. So DC1 with an IP of 10.0.0.0, had the first DNS entry as 10.0.0.0.

After I changed it to the new DNS server IP, I ran dcpromo again and it worked like a charm, no reboot needed. I did do a ipconfig /flushdns, just because though. Also, according to Microsoft you should not have a domain/DNS server pointing to itself as the first entry. The first DNS entry should be another DNS server, and use the local host address of 127.0.0.1 as the second entry. I won't go into detail as why, but a quick search should give you all you need. Enjoy!

How to: Server 2008R2 RDS Re-Arm for another 120 days.

You know, sometimes you just couldn't get that budget request in to get those RDS licenses ordered and installed. It happens, especially is this day in age. I searched everywhere on how to re-arm the trail for RDS, to no avail! All the answers I saw were, rebuild the server or buy the licenses. Sure, let me just rebuild a server just because (if that is an option, more power to you). Here is a simple way to re-arm the trail for RDS.

Locate in the registry editor and find this folder:
HKLM\SYS\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

Just delete the key inside this folder, reboot and you will have another 120 days to work with. Enjoy!

Xerox ColorQube/WorkCentre x86 driver on x64 Print Server

Hello everybody!

I am going to explain how to install a x86 Xerox driver on a x64 Print server.

Make sure you go to the Xerox driver page and download both the PS driver for x86 and x64. Install the x64 driver as usual with the print manager.

Now, for the x86 driver, it will ask for a i386 folder/destination. Here is where I got into trouble.

Called Xerox Support and they stated to download the GLOBAL 32 bit PS driver. For some reason, the Microsoft certified driver file does not contain the ntprint file that it needs to install the x86 driver.

As soon as I downloaded that Global print driver, I went through the install process again, this time when it asked for the i386, I pointed it to the global print driver folder and it found the ntprint file it needed. BAM, worked like a charm. Now my 9203 ColorQube is installed on my 2008R2 print server with both x86 and x64 drivers. Sweet.



Big thanks to Xerox for the quick call back and assistance.