Does ATI 2020 have a problem on W10 with Error 0xb042f?
I opened up my Wife's problem under acronis-true-image-2020-forum/last-2-attempts-do-back-have-failed-error and although not resolved by opening a Ticket, I was basically able to resolve it by changing the USB port. Or at least I thought I did. Came back again today. Twice. First I just rebooted the PC, thinking it didn't recognize the Drive (never checked). Then when the PC came up again, it failed. OK, did the power off/on of the PC. Then opened ATI and MANUALLY restarted it. It is working now.
Wife did get e-mail on the failure:
===============
On 5/6/2020 1:03:28 PM, e-mail address wrote:
2020-05-06T12:04:59:985-04:00 15676 I00000000: -----
2020-05-06T12:04:59:985-04:00 15676 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-05-06T12:05:00:054-04:00 15676 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-05-06T12:05:00:054-04:00 15676 I00640002: Operation LA-C, D, and E started manually.
2020-05-06T12:05:00:934-04:00 15676 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-05-06T12:05:00:941-04:00 15676 I013C0000: Operation: Backup
2020-05-06T12:05:00:941-04:00 15676 I0064000B: Priority changed to High.
2020-05-06T13:03:27:261-04:00 15676 E000B042F: Error 0xb042f: Destination is unavailable.
| trace level: error
| line: 0x5d5406763c32a94
| file: c:\bs_hudson\workspace\123\products\imager\archive\impl\operations\utils.cpp:582
| function: TrueImage::Archive::MakeDestinationUnavailableError
| line: 0x5d5406763c32a94, c:\bs_hudson\workspace\123\products\imager\archive\impl\operations\utils.cpp:582, TrueImage::Archive::MakeDestinationUnavailableError
| Path: M:\Acronis Backup\All_Drives\
| StrId: \local\hd_ev\vol_guid(F43039904D315EA7B59CAA8B53A01D31)
| $module: ti_demon_vs_25700
|
| error 0x2160015: A backup error.
| line: 0xa340ffd3416335cf
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353
|
================
I decided to look for "Error 0xb042f:" on Google as this might be a Win10 error code. Doesn't seem to be, unique to ATI possibly? I did find these 2 threads here:
error-0xb042f-destination-unavailable-acronis-2020
backup-failed
Neither have been solved it seems, other than the same thing, unplug, replug in the drive.
All three fail in the SAME PLACE...
Now maybe they should as the same code was exercised? But at least 3 users with a problem?
I doubt 3 PC's could have a h/w problem? In my case I changed USB ports, 2.0 and 3.0 and front and back ports. Our problem started 2 months ago I'd say, but the other links above were from Oct. and Dec. of last year.
Steve, if this was the case here, I'd understand it. It isn't though? I can read the drive after the fail without problems. I and my wife have NEVER had a problem reading that drive in Windows. I can't tell you how many things I looked at and test methods. ONLY ATI comes up with that error. EVENT VIEWER shows no errors... even when ATI tried to read it?
I've moved the drive to 5 different ports, and even used a USB HUB to connect it to, ALL FAIL eventually in ATI, but NOT in Windows.
Most of the time if ATI starts and connects, it finishes. Today was the first time that it didn't. Over 1 hour working and then the error, 57.1Mb written to the drive before failure.
If I didn't change from USB 3.0 to 2.0, and only one USB version had the problem, I'd suspect h/w problems, but I can't believe it would be both (different motherboard controllers and connectors). If it was only failing on the front or back connections, I'd believe a loose internal cable connection. However this is not the case.
With the drive connected and it fails, usually restarting will work, but sometimes it does require the drive be unplugged and plugged back it. However Windows can always read it when ATI fails...
This is an older PC, a 2012 Dell, an XPS8500, and Dell never verified it for W10, but this is the only problem program we have? I guess there could be a USB controller issue, but again, if there was Windows would have a problem, as well as the WD Utilities. I'm at a loss. One of the links I posted never got an answer either, just the same as we have to do, remove the drive and plug it in again. Odd.
In your case though it was immediate. After the Priority was changed, it took just over 3 and 1/2 minutes to determine the drive was 'disconnected. In my wife's case above, it was almost 1 hour as 57.1MB's were written before the failure. I don't even know what was going on on the PC? Could there have been an action requested by ATI and Windows didn't respond fast enough and ATI 'assumed' the drive was disconnected? Who knows?
I'm on her PC now... and went through the Event Viewer... and there WAS NO error around the same time as ATI had a problem reading the drive.
I do see some ATI errors though in the Event Viewer. See attached, and it is for ATIeRecord, but it seems it happens on every boot or shutdown? There seems to be at least 1 on every day. Google it seems relates it to AMD and she does have a Radeon video card...
So ATI has not produced anything.
Irv,
Sorry to hear you are still having issues with this. It really sounds to me like this drive is turning off causing this issue. I believe that in your last thread on this issue we looked at USB Selective Suspend in the PC Power Plan. If I am mistaken this feature needs to be disabled.
Besides Selective Suspend there are other places that you should investigate for power being shut off to the drive. I will outline them below:
- Disable the ability of the PC to Turn Off Mass Storage Devices.
- Open Windows Device Manager
- Go to Universal Serial Bus Controller > USB Mass Storage Device.
- Click to select the USB Mass Storage Device then right click and select Properties
- Click the Power Management tab and uncheck the box in front of Allow the computer to turn off this device to save power. Click OK the save the changes.
- Disable Legacy USB support in the PC BIOS.
- Press the Power button on the PC to turn on the device while rapidly pressing the F2 key to enter the BIOS setup screen.
- Look for USB configuration and select.
- Look for Legacy USB support and disable (if you find it here)
- Verify that all ports, Front, Rear, Top, are enabled
- Look for Power > Power Management - Verify that USB PowerShare in S4/S5 state is disabled. Verify that USB PowerShare in Sleep State is Normal
Additionally, I encourage you to visit the Dell link below for an FAQ on USB. There are some hints and tips there that may provide a solution.
Irv, looking at this thread and your prior one, it looks as though you are doing an Entire PC backup in that you are backing up three different drives on one backup task. It also looked like about a 10 hour backup job when all is OK. Am I correct?
If the failure is consistently happening at about the same spot in the backup, I'm wondering about it failing when moving on to the second (or third) source disk. Is it possible that the time it takes to build the image to backup is allowing the destination drive to be turned off.
Have you considered splitting the job into separate backups, one for each drive.
Enchantech, thanks for the reply. I did verify what you wanted checked. All set the way you said they should be.
I'm not sure the drive is being disabled? If it were, I'd see when it came back on-line? Windows normally would put up a pop-up stating it was ready I think? Also, after I did get the error the first thing I do it use Windows Explorer to access the drive, it worked every time.
Is it possible that ATI just isn't giving enough time for the disk to respond? I've tested it with the LONG test on the WD Utilities and it had found no problems?
One REAL oddity happened today. On my PC I had a Windows Update that wasn't required. I read the contents at MS, and although I didn't need it, I installed it on my PC. Since I had to reboot her PC to get to the BIOS, I noticed she had a fix to be installed (I did NOT?). It was "Apple, Inc - USBDevice - 5/7/2018 12:00:00 AM - 423.36"? What was that? From 2018? We both have Apple iPad's we backup on the PC's. So it must be port of iTunes? We both recently updated iTunes. Could this have something to do with it? Why didn't I have the same update on my PC (I am on Home, she has Pro, could have something to do with it?)?
BrunoC wrote:Irv, looking at this thread and your prior one, it looks as though you are doing an Entire PC backup in that you are backing up three different drives on one backup task. It also looked like about a 10 hour backup job when all is OK. Am I correct?
Yes, you are correct.
No, up until yesterday, all the fails were like Steve has shown, like the drive was not attached.
This time the fail was about an hour after the job started. Hard to tell where the process was, but the C: is small, and SSD using 70GB's. The D: is the killer, 460GB, and E:, 220GB's.
At the last fail point, 57.1GB's were written and the total job was 580GB's.
I did in the past, a little over a year ago, the C: drive alone, and it was only 33GB's. That drive is basically OS only. No full programs are usually installed to it. Based on that I would not think it was during a drive to save switch? However, if one assumes constant compression time on the drive contents, then maybe it was? C: is 'approximately' 10% of the total drive space being saved (although it is probably a lot less due to so much on C: that is NOT saved, like recycle bin, temp folders, etc). Even if it were happening on the backup drive to be handled, that would not explain why ATI would think the backup drive dropped?
This is NO setting I can find that will cause the USB drive to sleep? Well, not really. WD Utilities does have a setting for that when the drive is NOT in use, the time after it goes idle to turn off. Her's was ON with a 45 min. setting. I should mention, my USB drive on my PC is the same make and model and mine is set to 30 min., and I have never had the failure. My PC is a Dell XPS8700, about 2 years newer with a slightly faster CPU and RAM. My PC has also be certified by Dell for W10 as hers has not been (too old). Still, the problem only appeared in the last 2 months.
I did consider individual drives, but I didn't see the logic in doing that. All drives probably have programs that write to the C: drive? If so, if I needed to restore the PC I'd have do all the drives anyway? I know in certain circumstance only specific files might need to be recovered, and in those cases, individual backups would be fine. However, if C: needed to be recovered it was possible all drives would need to be recovered to match. Another reason was how to make this happen timing wise reasonably close together like a single job is? Bad enough now she might be using the PC while a backup is happening, and I'd want to manage possible differences due to file changes as little as possible?
I'm still questioning now why that OLD Apple USB file 'fix' had to be updated now? Why not my PC? Well, I guess it is, it ONLY appears in Device Manager when the iPad is connected. I even have the same dated driver. I can only assume it has nothing to do with the drive itself and for some reason either she didn't have it or it needed to be updated? Oddly enough, my PC never shows in the Update History of it being installed, but it does on her PC from today? Probably a 'red herring' I guess?
Irv, I have iTunes installed on my PC so I decided to look at the Device Manager for the USB controllers to see if I had that. While it didn't show up at first, I selected the "Show hidden devices" option and the only Apple device shown is Apple Mobile Device USB Driver, but the version is 6.0.9999.69 dated 5/19/2017. Looking at the events, it was installed on 4/29/2020. Looking further, I discovered that it was installed when I plugged in my old iPod Touch to charge it.
Anyway, I did read about reports from 2018 about the driver you referenced causing powering issues on USB ports and people uninstalled it.
All this makes me wonder if your issues could be USB driver related. Is the computer set up to automatically install drivers or does it ask first?
Also, pretty much all the drives you plug in will be listed in DM under Disk drive when you are showing hidden devices. It's generally pretty safe to uninstall the grayed out devices.
Irv,
Bruno makes great points with tagging the Apple driver as suspect. You can relate better than 90% of all problems with USB to driver issues.
I would uninstall that driver if it were me here and see if that fixes the issue. Then if it does go to the link provided below and download the MS fix for hiding/blocking updates from installation. With it you can specifically target this driver preventing it from installing again in the future.
Bruno, I did forget about the ability to see Hidden Devices...
With that I do see them on my PC now... just like when I plugged in my iPad.
There are 2, one the Composite Device, the other just the Device. Both the same version it seems, "423.36.0.0", dated "5/7/2018".
This is what I see:
By the way, it was Installed TODAY as well, but doesn't show on the Windows Update History of being installed? Now my wife's PC is completely different.
Note the number of dup's! Latest one each was 3/30/2020 (which I think is about the time her problems started possibly?). Note I do NOT have the 'iBoot' device either?
More driver info on her PC:
That is the same Properties on the TWO Composite Devices showing 2 different tabs that are the same data.
Again, the odd part on her PC in the Windows Update page:
I looked at the Events on EVERY Apple device on her PC, NONE, not one, has the same Install date?
NOTE: Her PC is the PRO edition, might explain some differences, not sure? Also this is an INTEL i7 PC, MS does seem to have TWO versions in its catalog of this driver. One is for an AMD CPU it seems, the other for Intel x86. Might explain the version differences.
Soooo.... at this point I'm going to wait on next weeks run. From the last capture I don't know if the driver was installed before or not at since the name is the same it might have been overlaid. The fact that I too have this driver, but DO NOT see it in my Update list makes me think it could be Home vs. Pro difference.
If it FAILS again, I think I'm going to UNINSTALL all the APPLE DRIVERS and then have Device Manager search for new items. I just can't explain the differences between my PC and her PC.
Enchantech, see the last reply.
Something seems off-base on her PC. Since the 'latest' driver installed today 'thinks' it is installed, I'll wait to next weeks backup. Any failure, I'll delete at the Apple drivers and see what happens? I'm sure those drivers will come back if they are still there, or if an iPad should be plugged in (we will see I guess)?
Don't know why old 'versions' remain though? I guess I could have plugged in her iPad (she IS using it) and see which device was then working? They all said they were not running as no device was attached? Possible if I were to plug it in another set for the latest install date would appear?
Still, I'm not sure if this is really a problem either? Bruno even had a different version, but maybe it is due to an AMD vs. Intel planar?
BrunoC wrote:Irv, I have iTunes installed on my PC so I decided to look at the Device Manager for the USB controllers to see if I had that. While it didn't show up at first, I selected the "Show hidden devices" option and the only Apple device shown is Apple Mobile Device USB Driver, but the version is 6.0.9999.69 dated 5/19/2017. Looking at the events, it was installed on 4/29/2020. Looking further, I discovered that it was installed when I plugged in my old iPod Touch to charge it.
Bruno, I can't find the version you have in the MS catalog, Apple USB files
Anyway, I did read about reports from 2018 about the driver you referenced causing powering issues on USB ports and people uninstalled it.
I wasn't able to locate these, but I did see about uninstalling them.
Irv,
Not sure about how Apple installs drivers. This sounds like each time you plug in the device the driver is installed again. If true that is sloppy!
You are correct in that once you plug the device in it will install the driver if not found. At this point I wonder if the problem Apple had with this driver thing was the fact that it would install anew each time the device was attached.
Running multiple same version drivers should not really cause issue I don't think. However, in the case of a backup taking place and during that backup the Apple device were attached and that triggers the install of the driver well, now that would be a problem as that would kill the connection to the backup drive.
I can't believe that Apple would release something like that but I guess such things do happen these days!
Enchantech, I can't believe it was Apple, otherwise my PC would have the same thing going on, and as the captures show, it doesn't?
I have to think this is really due to 'us' moving the USB drive from port to port. However, I don't think I hit that many, and ALL indicate the same port now? Could be a Home vs. Pro edition of Windows maybe?
We've never had a fail connecting the iPad to that PC, and certainly didn't do that during an ATI operation.
We've both had iPad 2, 4, and now Pro's. Wouldn't think that would make a difference, would you?
I'm also thinking that the driver, which does link to a port, would only 'apply' when the iPad was connected? The status for ALL of them says that it isn't active as a device isn't connected. Meanwhile, the USB drive is on its own port and never moved (usually).
Irv,
Okay, so maybe not Apple. I will say that MS, Apple, Adobe, you name it, these days the quality control is not what it once was.
Maybe Bruno can post more on his statement "Anyway, I did read about reports from 2018 about the driver you referenced causing powering issues on USB ports and people uninstalled it." Would be interesting to know more.
Have you tried a different USB cable from the PC to the USB drive? If not you might do so. I myself had one USB external drive that was intermittent connection for a bit. I found out if I moved the cable at the drive connection it would drop out some times. After awhile it quit totally so I know it was the connector in disk case. I cracked open the case, pulled the drive, and still use it as a spare from time to time.
Keep at it, hopefully you will discover what the issues is. :-)
Enchantech wrote:Have you tried a different USB cable from the PC to the USB drive? If not you might do so.
Good idea! WD's, at least this model, have a different proprietary cables. O can switch the cable with mine I guess if this happens again. That drive sits on top of the tower and isn't moved, and when the cable went to a back port, it wouldn't have moved either.
Since when I do remove the cable and plug it back in, ATI picks that up and then works fine. Another member said the same thing in his thread, so that would sort of rule out the cable 'logically'? I can't think of all her ports going 'bad' either? So I will try this, and deleting the Apple drivers, but I'd be surprised if it fixes the problem. W10 Home vs. Pro, again, I'd think the USB code couldn't care and probably is identical? The problem in my mind lies in ATI not handling a missed (timeout) response on a disk access or a plain timing issue. Port itself as well I guess but Windows Explorer doesn't have a problem. I know I sound like a broken record, but this has me totally perplexed? I am retired, but I was a programmer, and I've written disk code before and worked on an OS. It just doesn't seem like a h/w problem with all the moving of h/w around I did? Also only on one of two PC's here that are basically the same mostly.
To answer Enchantech's question about the error reports...
https://answers.microsoft.com/en-us/windows/forum/all/apple-inc-usbdevice-572018-120000-am-42336-affects/045c92ca-729c-4f92-8289-c2b054c368e2
As for seeing the installed drivers in Windows Update... I generally don't see them there. But the event history shown by the Device Manager properties is the best for seeing what happens when.
Check your drives in Device Manager as well as the USB Controllers. You'll probably see entries for the Apple as well as anything else you've plugged in. I went on an old battery charging spree last week and found entries for my iPod, Garmin, HTC phone and all the various drives. If they are grayed out, it should be safe to uninstall the device (and maybe the driver). I do know that when I plug many new devices in I get messages about drivers being installed.
As to Windows 10 Home vs Pro... maybe a culprit but I doubt it. BTW, I always go with the Pro version as it provides many more tools and controls on the system.
Irv says... "I am retired, but I was a programmer, and I've written disk code before and worked on an OS. It just doesn't seem like a h/w problem with all the moving of h/w around I did? Also only on one of two PC's here that are basically the same mostly." What you said about yourself exactly applies to me too, so I understand from where you are coming. That said, there are times I've been 100% sure, and yet find out I'm dead wrong (e.g. the reset backup task issue of last fall where my thinking was way off). The fact that the systems are "basically the same mostly" may lead nowhere. My wife's computer is basically the same mostly to mine and yet there are things I can never get to work right on one system or the other.
Anyway, my recommendation is to rid yourself of superfluous drivers and see if it works. Also, I would urge you to consider separating the backups into one for each disk. You can still schedule them for roughly the same time and the scheduler will assure that they run sequentially.
BrunoC wrote:To answer Enchantech's question about the error reports...
https://answers.microsoft.com/en-us/windows/forum/all/apple-inc-usbdevice-572018-120000-am-42336-affects/045c92ca-729c-4f92-8289-c2b054c368e2As for seeing the installed drivers in Windows Update... I generally don't see them there. But the event history shown by the Device Manager properties is the best for seeing what happens when.
Saw that link, and dismissed it, only pertains to an iPhone, and we never have had an iPad connected during ATI running.
I did check the all the driver event tab, one shown above. Nothing installed showing past 3/30/2020. I'll assume once my wife connects her iPad the new one will install?
Home vs. Pro, true, Pro has more 'built-in' controls. However most if not all can be handled via Registry changes. At one time there was even a GPEDIT available for the Home versions. The reason for the differences, that is what was shipped on our Dell's. I do see 'sales' not for Pro upgrades on Redmond Pie for about $13, but I don't even want to do that.
Trust me, I've been wrong before, more than once. I've had instances where I 'threw in the towel' so to speak trying to untangle messes in the OS and just either restored to a prior version or did a complete re-install (easier to do 'in-place' on older MS Windows versions).
Before I dump that drivers I'd sure like to know more about it, and why a Pro version didn't seem to delete the old ones?
I'm starting to think about this on a different track now too. It could very WELL be something I caused? Well, not really, but as a by product of what I did. See, my wife's PC has more USB devices than I do. She had both a usb keyboard and mouse, while I have a Logitech Integrated pair (she did NOT like the Logitech mouse and bought a vertical mouse which needed another USB port to connect to for its dongle (bluetooth). Due to this, a device had to be plugged into the front port which sticks out, and twice she knocked into it. Before any damage was done I bought 2 of these (USB Hub from Amazon. Put it on both our PC's. That allowed me to add the drive to a back 3.0 port. That was working for months. Once the problem with ATI hit I removed that thinking a possible MS Update might have caused it and since it drew power from the port, could be a problem. It wasn't. I then moved the drive to a few ports. Only odd thing I discovered, the backup was about 20% faster when connected to a USB 2.0 port? Also, that device could have caused Windows to mess up possibly? Buttons on the Hub does turn hub port off. I should note I have that device on my PC and do NOT see the multiple device I see on her PC, but I've never changed the port the drive is on on my PC.
Are you sure that ATI will run a backup sequentially when more than one tries to run at the same time? I don't recall seeing that documented?
I am thinking, or I should say rethinking the backup strategy on her PC? My backups are usually 2 hours or so. Hers are 10 hours. I make more system changes than she does too. Her are more game playing and mail, as well as browsing (which doesn't usually save much data). I've been using full backups once a week. Both of us have 4TB backup drives. I save 6 weekly iterations. On her PC, too much saved (her game folder is huge, she never deletes and after finishing them) so I only save 4 iterations. Since there isn't really a lot changed on her PC, a new game added, emails, USER folder updates, and randomly not much else, a versioning backup might be better. The primary would be as large as the backup that is produced now, but later versions would be quite small probably and could hold many more before a new set would be required. This is for another day though, right now, I need to have the failures fixed.
I did some more searching here, this problem is not isolated (I tried putting in links before but the forum s/w didn't like them, so I'll try again):
Unplug the drive and plug it in again
Same error, 10 minutes after start, no answer
Old one from me that appeared to fix itself in Feb.
Older one indicating the problem was fixed by and update, was it completely fixed?
Irv, if you are interested, I have created a small Powershell script that I have added to my own backup task where I have been seeing this issue so that this runs as a Pre Command to check the drive, dismount then mount it again (after 3 seconds), then continue the backup if OK.
The script takes the drive letter as a single parameter in the normal S: format and is launched from a .bat file. Both files attached below in a small zip file.
Steve, thanks, I've got it down.
I will still wait and see if I get a failure again. If so, I'll remove the Apple USB stuff, and then see if that clears it.
We seem to be having 2 failure scenario's. One is the drive isn't seen at start, the other, the drive drops during the backup process.
Actually, I probably will run that often on her PC as a test to see it the drive comes up immediately. It is quite possible the PC boot process doesn't actually get the USB drive up completely and that causes the first scenario. The 2nd one, a completely different story, and more troublesome.
Irv, I did not see a confirmation from you that you've configured the Power Management for your USB controllers to no longer allow the device to be turned off to save power (as Steve outlined in reply #4 above). Have you done that for all USB controllers that have the Power Management tab?
Additionally, there is a feature in the power scheme advanced settings called USB selective suspend setting. Have you tried to disable that? (This is accessed through Control Panel power settings.)
Finally, try checking the "Notify me if there are issues connecting to USB devices" in settings.
Bruno, I thought I had said I confirmed the USB Controller settings? Checked again, ALL with the capability to turn it off are UNCHECKED.
Now, maybe you hit on something? The Selective Suspend. On my PC it is DISABLED. Hers, it shows as ENABLED. I've changed that now to DISABLED as well. That one would make sense being the cause of the fail on start, drive could be powered down (although according to the WD Drive Utility both drives we have are set to NOT POWER DOWN) as I think the OS overrides the WD setting? However, that would not be the cause if the drive was in use, like a fail in the backup taking place I'd think.
Again, we'll see what happens next week.
For what it is worth, my backup ran today (OK) and it only took 2 1/2 hours:
============
2020-05-08T09:19:09:295-04:00 9656 I00000000: -----
2020-05-08T09:19:09:295-04:00 9656 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-05-08T09:19:09:535-04:00 9656 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-05-08T09:19:09:537-04:00 9656 I00640002: Operation My disks started by schedule.
2020-05-08T09:19:13:670-04:00 9656 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-05-08T09:19:13:690-04:00 9656 I013C0000: Operation: Backup
2020-05-08T09:19:13:690-04:00 9656 I0064000B: Priority changed to Low.
2020-05-08T11:44:12:713-04:00 9656 I013C0006: Operation has succeeded.
===============
It used 234GB's for the backup. Hers took 10 hours on a 589GB backup, but I suspect a lot more work has to be done on her games that are probably already packed?
Steve Smith wrote:Irv, if you are interested, I have created a small Powershell script that I have added to my own backup task where I have been seeing this issue so that this runs as a Pre Command to check the drive, dismount then mount it again (after 3 seconds), then continue the backup if OK.
The script takes the drive letter as a single parameter in the normal S: format and is launched from a .bat file. Both files attached below in a small zip file.
Steve, I modified it to match the drive letter in both our PC's. Then ran it and echo'ed the output to a file.
Run OK on my PC without a problem.
However the first time I ran it on her PC it reported the drive was NOT available!!!! 2nd time it worked fine:
============================
Creates, deletes, or lists a volume mount point.
MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
MOUNTVOL [drive:]path /P
MOUNTVOL /R
MOUNTVOL /N
MOUNTVOL /E
path Specifies the existing NTFS directory where the mount
point will reside.
VolumeName Specifies the volume name that is the target of the mount
point.
/D Removes the volume mount point from the specified directory.
/L Lists the mounted volume name for the specified directory.
/P Removes the volume mount point from the specified directory,
dismounts the volume, and makes the volume not mountable.
You can make the volume mountable again by creating a volume
mount point.
/R Removes volume mount point directories and registry settings
for volumes that are no longer in the system.
/N Disables automatic mounting of new volumes.
/E Re-enables automatic mounting of new volumes.
Possible values for VolumeName along with current mount points are:
\\?\Volume{be9fa1b5-0000-0000-0000-602200000000}\
C:\
\\?\Volume{336e52d0-209c-4871-9896-369f15ca52d7}\
F:\
\\?\Volume{56716620-0000-0000-0000-800200000000}\
*** NO MOUNT POINTS ***
\\?\Volume{f4303990-5ea7-4d31-8baa-9cb5311da053}\
M:\
\\?\Volume{56716620-0000-0000-0014-341323000000}\
D:\
\\?\Volume{56716620-0000-0000-0082-4813a0000000}\
E:\
\\?\Volume{be9fa1b5-0000-0000-0000-100000000000}\
*** NO MOUNT POINTS ***
\\?\Volume{56716620-0000-0000-0000-801203000000}\
*** NO MOUNT POINTS ***
\\?\Volume{3874fc92-f7d9-11e7-a9b5-806e6f6e6963}\
H:\
\\?\Volume{3874fc94-f7d9-11e7-a9b5-806e6f6e6963}\
I:\
\\?\Volume{3874fc95-f7d9-11e7-a9b5-806e6f6e6963}\
J:\
\\?\Volume{3874fc96-f7d9-11e7-a9b5-806e6f6e6963}\
K:\
\\?\Volume{3874fc7f-f7d9-11e7-a9b5-806e6f6e6963}\
P:\
USB drive letter M: mounted
===============
Like I said, the first time it failed and I got an error Dialog box telling me that!
I just checked the Event Viewer, no error? I waited 1/2 hour and ran the test again, same result as above.
Now I wonder about the Suspend setting that was ENABLED?
After an MS Update she had some 'weird' things happening. Like some apps lost settings. I did find some changes for the disk wind down and display turn-off as well as the ScreenSaver were missing? Could something during the update changed more than I found? We both have the Hard Disk set to turn-off after 20 minutes, but I am sure this is physical bus connected hard drives, not USB drives or devices.
I'll keep an eye on the drive and run the BAT file occasionally. Could be the answer to her problem, either the drive did power down or it never really started?
Steve, I was playing with your files. My PC has the USB drive on P:. You have it on S:
When I altered your file, I changed the path to the PS command to a temp folder with both files were. That produced the output I listed. Then I saw you supplied S: the BAT file in ATI... OK, I'll put it back to S: from P: that I changed the PS file to. Ran the BAT file with the parameter P: and output the results to a TXT file.
Much to my SURPRISE was this:
==============
USB drive letter S: mounted
============
Uhh, I don't have an S: drive?
This is the command I issued "K:\Inet DL\537603-183798>checkusbdisk P: >test.txt"
Changed BAT file (just the path to the PS1 file):
==============
@echo off
set PS="c:\windows\system32\WindowsPowerShell\v1.0\powershell.exe"
set task="K:\Inet DL\537603-183798\CheckUSBdisk.ps1"
%PS% -ExecutionPolicy RemoteSigned -windowstyle Hidden -file %task%
===============
No change made to the PS1 file, and I got the line above as a result. When I did change this line to P:
===========
[string]$drive = 'S:')
============
On my PC it told me my P: drive was mounted.
On my wife's PC, it was changed to M: and I got the diaog box error the first time and then it worked correctly.
However, since I don't have an S: drive, I wonder why it told me it was mounted and if any result would be 'real'? Maybe only the one when the drive is there but NOT mounted which caused the error box?
I waited 1/2 hour and tried it again on my wife's PC, still mounted?
Irv, one particular point from your last post. If you are using drive M: for your USB drive, then please be aware that this is also used by the Acronis Drive feature used by ATI for doing Mobile backups and is a real issue to get the latter to change!
See KB 59584: Acronis True Image 2017: how to change Acronis Drive letter - for more details on the above.
If you do use the Mobile backup feature, then consider changing your USB backup drive to another drive letter later in the alphabet.
Irv, there shouldn't be a need to change the .ps1 file as the first part of the script is setting up to receive a parameter when called.
param(
[ValidatePattern("\w\:")]
[string]$drive = 'S:')
The third line above will set $drive to the parameter value passed, else it will default to S: if no parameter is given.
Irv,
The PC having Selective Suspend enabled is very likely to be the root cause of the behavior you see in both instances on this PC. I mentioned disabling that in my post #4 above, guess you missed it.
Speaking of Selective Suspend, do you find an entry in the Power Settings for Hub Selective Suspend? If so you should probably remove it as desktop PC do not need it. On some older PC's I have seen Windows 10 mistake a desktop for a laptop and that would bring this setting into play.
Below is a guide on how to handle Hub Selective Suspend if you have it showing.
Steve, I'm sitting here looking at your PowerShell script referenced above and have a few questions about it...
1. In your pre-command you pass S: as an argument, but I don't see the argument to CheckUSBdisk.bat being passed on to CheckUSBdisk.ps1
2. In CheckUSBdisk.ps1, if the first test-path fails, the else clause uses $volid which does not appear to be set yet.
Bruno, you are correct that the script expects a drive letter to be passed as a parameter (as shown in the screen shot from my Pre Command earlier).
I have updated the script to better handle the case where the drive isn't found and therefore no volid is given for it.
Version 2 is attached below: The user would need to set the value for variable $lastvolid at the top of the script by running the mountvol $drive /l command to find the known volid.
Note: I am not passing any parameter within the .bat file, this would need to be either added or else called with the bat file:
CheckUSBdisk.bat S:
(as being used in the Pre Command example image).
Steve Smith wrote:If you do use the Mobile backup feature, then consider changing your USB backup drive to another drive letter later in the alphabet.
Steve, been using on her PC the USB drive set to M: 'forever'. This is also a desktop, not a laptop nor mobile device and I've never used Mobile.
Do I need to change the drive anyway?
Steve, on the new set of files, I am calling it like this, "checkusbdisk p > testout.txt" but it seems the P: isn't being passed?
I get this:
=========
S: not found, using \\?\Volume{a7fdbf40-0000-0000-0000-100008000000}\
The parameter is incorrect.
USB drive letter S: attempted to be mounted
USB drive letter S: mount failed!
==========
Of course part of the problem I've not changed the $lastvolid.
So I ran this PS command, PS C:\> mountvol $drive /l and found my P: drive data:
\\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\ --- P:\
Inserted that into the line in the PS1 file: $lastvolid = '\\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\'
Ran it using the above command and got this:
===========
S: not found, using \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
Access is denied.
USB drive letter S: attempted to be mounted
USB drive letter S: mount failed!
============
Note, it was run using checkusbdisk p > testout.txt so p wasn't passed. So I changed S to p in the PS1 file. Failed again:
=============
p: not found, using \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
The directory is not empty.
USB drive letter p: attempted to be mounted
USB drive letter p: mount failed!
==============
The prior code (2nd released) worked fine though?
Irv Spalten wrote:Steve, been using on her PC the USB drive set to M: 'forever'. This is also a desktop, not a laptop nor mobile device and I've never used Mobile.
Do I need to change the drive anyway?
If you don't use the Acronis Mobile Backup app from an Android or Apple mobile phone to backup to your PC, then Acronis Drive should not be active, so no need to change the drive letter from M:
Irv Spalten wrote:Steve, on the new set of files, I am calling it like this, "checkusbdisk p > testout.txt" but it seems the P: isn't being passed?
Irv, you should be using "checkusbdisk p: > testout.txt" (including the colon).
The second updated script posted here is the one you should be using after changing the line indicated at the top via the lines:
# The value for $lastvolid is found by using 'mountvol $drive /l' when drive is connected.
$lastvolid = '\\?\Volume{a7fdbf40-0000-0000-0000-100008000000}\'
The value shown above is from my S: external drive, so you need to find this for your M: drive by running: mountvol M: /l and copying the output value to the script.
If you are still seeing the error:
p: not found, using \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
The directory is not empty.
USB drive letter p: attempted to be mounted
USB drive letter p: mount failed!
Then check in Explorer for the drive and look at the size? If it shows as 0 (zero) then you need to physically disconnect & reconnect the drive for it to register correctly.
Steve Smith wrote:Irv Spalten wrote:Steve, on the new set of files, I am calling it like this, "checkusbdisk p > testout.txt" but it seems the P: isn't being passed?
Irv, you should be using "checkusbdisk p: > testout.txt" (including the colon).
The second updated script posted here is the one you should be using after changing the line indicated at the top via the lines:
# The value for $lastvolid is found by using 'mountvol $drive /l' when drive is connected.
$lastvolid = '\\?\Volume{a7fdbf40-0000-0000-0000-100008000000}\'The value shown above is from my S: external drive, so you need to find this for your M: drive by running: mountvol M: /l and copying the output value to the script.
If you are still seeing the error:
p: not found, using \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
The directory is not empty.
USB drive letter p: attempted to be mounted
USB drive letter p: mount failed!Then check in Explorer for the drive and look at the size? If it shows as 0 (zero) then you need to physically disconnect & reconnect the drive for it to register correctly.
Steve, I accidentally marked the THREAD as SOLVED, it isn't really (original part). Can you change that as it seems I can not?
Well, one of two things 'fixed' this PS1 problem, and really not sure which?
I did use the 'p;' this time, but also used an elevated command prompt run as Administrator.
Got this:
--------------
The volume is still in use. A force dismount was issued and current handles
to the volume have been invalidated.
USB drive letter p: removed
USB drive letter p: mounted
---------------
Was in use as I had Explorer running I guess?
Suspect I needed the elevated Administrator prompt? Ran it in a normal prompt with just 'p' as the parameter.
--------------
The volume is still in use. A force dismount was issued and current handles
to the volume have been invalidated.
Access is denied.
USB drive letter p: removed
The directory is not empty.
USB drive letter p: mounted
USB drive letter p: mount failed!
--------------
Note I got different results and both a mount and fail?
Tried again, not an Administrator CMD prompt and p: as the parameter.
--------------
p: not found, using \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
The directory is not empty.
USB drive letter p: attempted to be mounted
USB drive letter p: mount failed!
---------------
Just to be clear, this IS the PS1 code I'm running:
------------------------
param(
[ValidatePattern("\w\:")]
[string]$drive = 'p:') #$drive will default to S: if no parameter provided on call to script
# The value for $lastvolid is found by using 'mountvol $drive /l' when drive is connected.
$lastvolid = '\\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\'
# -------------------------------------------------------------------------------
if (test-path $drive) {
$volid = (mountvol $drive /l)
$volid = $volid.Trim()
mountvol $drive /P
Write-Host "USB drive letter $drive removed"
start-sleep -Seconds 3
mountvol $drive $volid
Write-Host "USB drive letter $drive mounted"
} else {
Write-Host "$drive not found, using $lastvolid"
mountvol $drive $lastvolid
Write-Host "USB drive letter $drive attempted to be mounted"
}
# -------------------------------------------------------------------------------
if (test-path $drive) {exit 0} else {
Write-Host "USB drive letter $drive mount failed!"
exit 1}
--------------------
Irv, sorry but I am not aware of how to change the 'Solved' status once it has been set by the OP of a topic.
The Powershell script should be run as Administrator, which is how I normally run it when testing it using the Powershell ISE as Administrator.
Figured that it would need to be. ATI runs as an Administrator so that is what clued me in.
Probably need to change the script, adding
PS> Start-Process powershell.exe -Verb runAs
to start it as Admin I guess?
Steve, I figured that as ATI runs elevated...
Can add this to the script to force it:
PS> Start-Process powershell.exe -Verb runAs
Steve, I tried the ISE as I wanted to step through the commands. Got an error:
PS C:\Users\ispal_000> K:\Inet DL\537649-183809\CheckUSBdisk.ps1
File K:\Inet DL\537649-183809\CheckUSBdisk.ps1 cannot be loaded. The file K:\Inet DL\537649-183809\CheckUSBdisk.ps1 is not digitally signed. You cannot run this script
on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
+ CategoryInfo : SecurityError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnauthorizedAccess
Guess I could add one of these to it?
Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope LocalMachine
pwsh.exe -ExecutionPolicy AllSigned
To run the script I prefer to use the Powershell ISE (run as Administrator) but the default security settings for most users will prevent any unsigned scripts from being run unless you have created a Powershell profile and set a different execution policy to allow scripts to run.
For Powershell ISE the profile document is stored at:
$env:HOMEPATH\Documents\WindowsPowerShell
in document: Microsoft.PowerShellISE_profile.ps1
The contents of this profile document need to include the following line at a minimum:
Set-executionpolicy -executionpolicy RemoteSigned process
Steve, I do not have Microsoft.PowerShellISE_profile.ps1 on my PC? $env:HOMEPATH\Documents\WindowsPowerShell should be in C:\USERS\MyID, but it isn't in Documents (no folder). Am I to create the folder and file? Been sometime since I played with PowerShell to do anything complex.
Irv, see webpage: PowerShell for Beginners (Part 6): PowerShell Profiles and the ISE - which I have bookmarked from when I first started using PowerShell and needed to setup my own ps profiles rather than having to set things every time.
Thanks, I see I had to create that file via PowerShell. Did that and added the line.
I start looking at it later.
I guess I'm not as smart as I think I am? I did create the file with the line in it in the correct place.
Then tried again in the ISE, first got the same run problem, and once I put the line in as a command it ran, but still failed, and I ran this under an Administrator prompt on my PC:
PS C:\WINDOWS\system32> K:\Inet DL\537649-183809\CheckUSBdisk.ps1
File K:\Inet DL\537649-183809\CheckUSBdisk.ps1 cannot be loaded. The file K:\Inet DL\537649-183809\CheckUSBdisk.ps1 is not digitally signed. You cannot run this script
on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
+ CategoryInfo : SecurityError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnauthorizedAccess
PS C:\WINDOWS\system32> Set-executionpolicy -executionpolicy RemoteSigned process
PS C:\WINDOWS\system32> K:\Inet DL\537649-183809\CheckUSBdisk.ps1
p: not found, using \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
The directory is not empty.
USB drive letter p: attempted to be mounted
USB drive letter p: mount failed!
PS C:\WINDOWS\system32>
Confused... P: is correct? \\?\Volume{0301534b-fdb8-48af-8914-2a11a8e2c77e}\
Irv, did you run the command:
New-Item -ItemType File -Path $Profile -Force
to create the profile in the correct place?
After doing so, use the command:
notepad $profile
to edit the contents of the profile and check what you have shown there?
My own profile looks as below:
# Steve's PowerShellISE profile
# Saved in "D:\Docs\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1"
# Set-executionpolicy -executionpolicy Bypass process
Set-executionpolicy -executionpolicy RemoteSigned processWrite-Host 'Welcome to' "$env:computername" -ForegroundColor Green
Write-Host "You are logged in as" "$env:username" -ForegroundColor Green
Write-Host "Today:" (Get-Date) -ForegroundColor Green
Set-Location d:\powershell\
Write-Host "PowerShell"($PSVersionTable.PSVersion.Major)"awaiting your commands."function edit ($file) {
if (Test-Path ${env:ProgramFiles(x86)}\Notepad++\notepad++.exe) {
& "${env:ProgramFiles(x86)}\Notepad++\notepad++.exe" $file}
else {
if (Test-Path $env:ProgramFiles\Notepad++\notepad++.exe) {
& "${env:ProgramFiles}\Notepad++\notepad++.exe" $file}
else {& "notepad.exe" $file }
}}Get-executionpolicy
Yes, I did, and still having some problems Steve... some of it might be differences in where some stuff gets stored and basic permissions.
I have been able to created the files in the proper place. Problem I had was my CMD running as Administrator opened to C:\Windows\System32. That put $Profile.txt there from the notepad++ $profile command.
However, when I exited and changed the prompt to C: it did put it where it was supposed to be.
OK, added your code to the profile, had to change stuff though to point to my PC's locations.:
========
# Irv's PowerShellISE profile
# Saved in "C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1"
# Set-executionpolicy -executionpolicy Bypass process
Set-executionpolicy -executionpolicy RemoteSigned process
Write-Host 'Welcome to' "$env:computername" -ForegroundColor Green
Write-Host "You are logged in as" "$env:username" -ForegroundColor Green
Write-Host "Today:" (Get-Date) -ForegroundColor Green
Set-Location d:\powershell\
Write-Host "PowerShell"($PSVersionTable.PSVersion.Major)"awaiting your commands."
function edit ($file) {
if (Test-Path ${env:ProgramFiles(x86)}\Notepad++\notepad++.exe) {
& "${env:ProgramFiles(x86)}\Notepad++\notepad++.exe" $file}
else {
if (Test-Path $env:ProgramFiles\Notepad++\notepad++.exe) {
& "${env:ProgramFiles}\Notepad++\notepad++.exe" $file}
else {& "notepad.exe" $file }
}}
Get-executionpolicy
=========
Didn't create the D:\POWERSHELL folder. will later, assume you save stuff there. Need to change my NOTEPAD++ location as well, but didn't think this would stop anything?
So I start POWERSHELL and get this:
===============
C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
. : File C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be
loaded. The file C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
is not digitally signed. You cannot run this script on the current system. For more information
about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShel ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
PS C:\>
======
This appears to be the line it is choking on?
Set-executionpolicy -executionpolicy RemoteSigned process so I read the link and I need the commented line above it, Set-executionpolicy -executionpolicy Bypass process. Change the comment character on it and made the other a comment. Still fails?
Can open ISE without an error though?
Irv, when you have ISE open, run the command: Get-ExecutionPolicy then look at what is returned?
Welcome to STEVE-9OP3KKF0
You are logged in as smiths
Today: 10/05/2020 17:42:41
PowerShell 5 awaiting your commands.
RemoteSignedPS D:\powershell> Get-ExecutionPolicy
RemoteSigned
The above was executed from the lower panel of ISE with the first part showing that the profile was executed on opening ISE then the Get-ExecutionPolicy command repeated separately.
You can edit your profile directly in ISE by using the command: psEdit $profile which will load the profile into the top ISE panel.
Steve, ran it,
=========
PS C:\> get-executionpolicy
AllSigned
PS C:\>
==========
RemoteSigned is for Windows Server it seems, so I changed it to AllSigned which is basically nothing.
I never created the D: folder, nor pointed to NOTEPAD++, so that should also fail.
Did try it in the ISE, but it seems to be a different story there,
=============
PS C:\> psEdit -filenames $profile
dir : Cannot find path 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1' because it does not exist.
At line:6 char:9
+ dir $filename | where {!$_.PSIsContainer} | %{
+ ~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Users\ispal_...ISE_profile.ps1:String) [Get-ChildItem], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
PS C:\>
==============
I don't have that profile, I copied everything to the "Microsoft.PowerShell_profile.ps1". Shouldn't that work,?
Do I need a Powershell profile or both a Powershell and ISE profile? If so, what should be in the PowerShell one?
I don't know why I'm having these problems, this should be easier than using just PowerShell?
Thanks for your help here, appreciate it.
By the way, I couldn't ever get the P: drive to re-mount, no matter what command I tried after I had dismounted it. Has to fire up DiskMgmt.MSC to assign it back to P:. Something about the GUID is a problem, the parameter itself being used? I did get some runs where the PS1 file did say it was mounted as I posted before? That was one reason I wanted to use DEBUG to step through the commands.
Irv, sorry but setting the ExecutionPolicy to AllSigned is the issue here!
See webpage: PowerShell – Running scripts is disabled on this system.
Below is the list of four different execution policies in PowerShell
- Restricted – No scripts can be run.
- AllSigned – Only scripts signed by a trusted publisher can be run.
- RemoteSigned – Downloaded scripts must be signed by a trusted publisher.
- Unrestricted – All Windows PowerShell scripts can be run.
And webpage: PowerShell ps1 is not digitally signed. You cannot run this script - which has a complete list of the options for ExecutionPolicy.
I normally use RemoteSigned which seems to work best for me.
I looked at the URL listed, had this:
========
Default
- Sets the default execution policy.
- Restricted for Windows clients.
- RemoteSigned for Windows servers.
RemoteSigned
- The default execution policy for Windows server computers.
- Scripts can run.
- Requires a digital signature from a trusted publisher on scripts and configuration files that are downloaded from the internet which includes email and instant messaging programs.
- Doesn't require digital signatures on scripts that are written on the local computer and not downloaded from the internet.
- Runs scripts that are downloaded from the internet and not signed, if the scripts are unblocked, such as by using the
Unblock-Filecmdlet. - Risks running unsigned scripts from sources other than the internet and signed scripts that could be malicious.
Restricted
- The default execution policy for Windows client computers.
- Permits individual commands, but does not allow scripts.
- Prevents running of all script files, including formatting and configuration files (
.ps1xml), module script files (.psm1), and PowerShell profiles (.ps1).
==================
I took it as REMOTESIGNED was 'only' for Windows Server PC's?
It said this for ALLSIGNED:
================
AllSigned
- Scripts can run.
- Requires that all scripts and configuration files be signed by a trusted publisher, including scripts that you write on the local computer.
- Prompts you before running scripts from publishers that you haven't yet classified as trusted or untrusted.
- Risks running signed, but malicious, scripts.
==============
I thought I'd be asked based on the next to last line? I did leave the REMOTESIGNED before and had problems.
Still getting that error too, as this is all in the ISE profile, but I have NO PS profile now?